[Hibernate-JIRA] Created: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used
8:32 a.m.
@SQLInsert. Columns in sql comes in different order depending on the application server
used
--------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also come
in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
4:08 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
Emmanuel Bernard commented on ANN-551:
--------------------------------------
I agree with you,it's annoying, but I don't think this is related to the way
addElemetsOfAClass add new elements, it worth a try though.
Did you use the same VM?
@SQLInsert. Columns in sql comes in different order depending on the
application server used
--------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
4:10 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
Emmanuel Bernard commented on ANN-551:
--------------------------------------
Since you have both environment, do you think you could give a shot to the
annotatedClass.getDeclaredProperties( accessType ) list reordering (by adding the code in
addElementsOfAClass), that would be awesome
@SQLInsert. Columns in sql comes in different order depending on the
application server used
--------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
7:06 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
Søren Pedersen commented on ANN-551:
------------------------------------
I used the same java version. I also tried swiching between 1.5.0_06 and 1.5.0_08 and it
resulted in yet another ordering of the properties.
I will try to put the some reordering code in there and get back to you.
@SQLInsert. Columns in sql comes in different order depending on the
application server used
--------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
9:50 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
Søren Pedersen commented on ANN-551:
------------------------------------
Hi Emmanuel,
I have now tried to reorder the list in the following manner in class AnnotationBinder:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
------ new code begin --------
Collections.sort(properties, new Comparator() {
public int compare(Object obj, Object obj1) {
String fileEntry1 = ((XProperty)obj).getName();
String fileEntry2 = ((XProperty)obj1).getName();
return fileEntry1.compareTo(fileEntry2);
}
});
------ new code begin --------
for ( XProperty p : properties ) {
It works!!
I have tested on both WebLogic 9.2 and JBoss 4.0.5 and with different java-versions.
Do you think it will be included in the next release?
Regards,
Søren
@SQLInsert. Columns in sql comes in different order depending on the
application server used
--------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
11:56 p.m.
New subject: [Hibernate-JIRA] Updated: (ANN-551) Guaranty the same parameter ordering when overriding SQL across VMs and compilations (Søren Pedersen)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=all ]
Emmanuel Bernard updated ANN-551:
---------------------------------
Summary: Guaranty the same parameter ordering when overriding SQL across VMs and
compilations (Søren Pedersen) (was: @SQLInsert. Columns in sql comes in different order
depending on the application server used)
Fix Version: 3.2.2
Assign To: Emmanuel Bernard
Yes, I added the code :-)
Guaranty the same parameter ordering when overriding SQL across VMs
and compilations (Søren Pedersen)
-----------------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Assignee: Emmanuel Bernard
Fix For: 3.2.2
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
11:56 p.m.
New subject: [Hibernate-JIRA] Resolved: (ANN-551) Guaranty the same parameter ordering when overriding SQL across VMs and compilations (Søren Pedersen)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=all ]
Emmanuel Bernard resolved ANN-551:
----------------------------------
Resolution: Fixed
Guaranty the same parameter ordering when overriding SQL across VMs
and compilations (Søren Pedersen)
-----------------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss
4.0.5. Oracle 10.
Reporter: Søren Pedersen
Assignee: Emmanuel Bernard
Fix For: 3.2.2
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) Guaranty the same parameter ordering when overriding SQL across VMs and compilations (Søren Pedersen)
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
todd orr commented on ANN-551:
------------------------------
Would it be possible to add named parameter support? This would get around this problem in
a much more decoupled fashion - no need to determine what order hibernate is trying to
insert by beforehand.
Guaranty the same parameter ordering when overriding SQL across VMs
and compilations (Søren Pedersen)
-----------------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Issue Type: Bug
Components: binder
Affects Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and
JBoss 4.0.5. Oracle 10.
Reporter: Søren Pedersen
Assignee: Emmanuel Bernard
Fix For: 3.3.0.ga
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-551) Guaranty the same parameter ordering when overriding SQL across VMs and compilations (Søren Pedersen)
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-551?page=co...
]
Max Rydahl Andersen commented on ANN-551:
-----------------------------------------
it's not trivial. needs to be fixed in hibernate core. contributions welcome ;)
Guaranty the same parameter ordering when overriding SQL across VMs
and compilations (Søren Pedersen)
-----------------------------------------------------------------------------------------------------
Key: ANN-551
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551
Project: Hibernate Annotations
Issue Type: Bug
Components: binder
Affects Versions: 3.2.1
Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and
JBoss 4.0.5. Oracle 10.
Reporter: Søren Pedersen
Assignee: Emmanuel Bernard
Fix For: 3.3.0.ga
Problem:
The columns in the sql you specify in SQLInsert annotation has be ordered in the same way
hibernate sorts its properties when constructing the insert sql.
Example:
When WebLogic 9.2 is used the sql should look like this:
"insert into acount (name, address, country) values (?,?,?)"
But when JBoss 4.0.5 is used the sql should look like this:
"insert into acount (address, country, name) values (?,?,?)"
The above are only examples.
Consequence:
I have to have different SQLInsert's for every JEE apllication server we support,
because the properties comes in different order depending on the application server used.
Suggested solution:
In the method
org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements,
PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final
XClass annotatedClass, ExtendedMappings mappings)
This property list shown below should be sorted to make sure that the properties also
come in the same order:
List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5875
days inactive
6296
days old
hibernate-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Emmanuel Bernard (JIRA) -
Max Rydahl Andersen (JIRA)
-
Søren Pedersen (JIRA)
-
todd orr (JIRA)