[Hibernate-JIRA] Created: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
9:04 p.m.
Projections that have aliases same as the property name result in invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER this_
order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If I
don't specify the alias or even change the value then it will produce a valid query it
just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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:21 p.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Shawn Clowater edited comment on HHH-5063 at 4/1/10 9:21 PM:
-------------------------------------------------------------
If I hack in this it actually works as I expected, I am prepending my aliases with x and
then stripping them off with this:
{code}
private class HackResultTransformer extends AliasToBeanResultTransformer{
public HackResultTransformer(Class resultClass) {
super(resultClass);
}
@Override
public Object transformTuple(Object[] tuple, String[] aliases) {
String[] cleanedUpAliases = new String[aliases.length];
for (int i = 0; i < aliases.length; i++){
cleanedUpAliases[i] = aliases[i].replaceFirst("x",
"");
}
return super.transformTuple(tuple, cleanedUpAliases);
}
}
{code}
was (Author: sclowater):
If I hack in this it actually works as I expected, I am prepending my aliases with x
and then stripping them off with this:
private class HackResultTransformer extends AliasToBeanResultTransformer{
public HackResultTransformer(Class resultClass) {
super(resultClass);
}
@Override
public Object transformTuple(Object[] tuple, String[] aliases) {
String[] cleanedUpAliases = new String[aliases.length];
for (int i = 0; i < aliases.length; i++){
cleanedUpAliases[i] = aliases[i].replaceFirst("x",
"");
}
return super.transformTuple(tuple, cleanedUpAliases);
}
}
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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:21 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Shawn Clowater commented on HHH-5063:
-------------------------------------
If I hack in this it actually works as I expected, I am prepending my aliases with x and
then stripping them off with this:
private class HackResultTransformer extends AliasToBeanResultTransformer{
public HackResultTransformer(Class resultClass) {
super(resultClass);
}
@Override
public Object transformTuple(Object[] tuple, String[] aliases) {
String[] cleanedUpAliases = new String[aliases.length];
for (int i = 0; i < aliases.length; i++){
cleanedUpAliases[i] = aliases[i].replaceFirst("x",
"");
}
return super.transformTuple(tuple, cleanedUpAliases);
}
}
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
12:13 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Gail Badner reassigned HHH-5063:
--------------------------------
Assignee: Gail Badner
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
10:53 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Shawn Clowater updated HHH-5063:
--------------------------------
Attachment: HHH-5063-testcase.patch
Small testcase that reproduces the sql error.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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:17 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Gail Badner commented on HHH-5063:
----------------------------------
Hi Shawn,
I've checked a fix into trunk. Can you give it a try?
Thanks,
Gail
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
10:37 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Shawn Clowater commented on HHH-5063:
-------------------------------------
Gail,
Sure, give me a bit to haul down and compile, etc.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
1:10 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Shawn Clowater commented on HHH-5063:
-------------------------------------
Gail, backpatched this to my local ver of 3.5.0 final and it looks like it works fine for
the one criteria that i had to initially work around. Running my full suite now to see if
anything else comes off the rails.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
10:11 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Gail Badner resolved HHH-5063.
------------------------------
Resolution: Fixed
From Shawn Clowater by irc:
(07:48:50 PM) sclowater: gbadner:
all seems well with the projection gear
Fixed in trunk.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
8:37 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Strong Liu commented on HHH-5063:
---------------------------------
http://hudson.qa.jboss.com/hudson/job/hibernate-core-branch35-testsuite/1...
fails
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
10:16 a.m.
New subject: [Hibernate-JIRA] Reopened: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Steve Ebersole reopened HHH-5063:
---------------------------------
Hudson shows this either not fixed or causing a regression. Also, no fix-for version was
specified...
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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:33 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Gail Badner updated HHH-5063:
-----------------------------
Fix Version/s: 3.6
3.5.2
I've checked the unit test output. The query is generated properly:
select count(distinct this_.address_city, this_.address_state) as y0_
from Student this_
The problem is that SQLServer only supports one argument in SELECT COUNT( DISTINCT ...).
I'll update the unit test to expect the exception for SQL Server and any other
dialects that show this failure.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Fix For: 3.5.2, 3.6
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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:32 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-5063) Projections that have aliases same as the property name result in invalid sql
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063?page=c...
]
Gail Badner resolved HHH-5063.
------------------------------
Resolution: Fixed
The unit tests will be fixed by HHH-5220.
Projections that have aliases same as the property name result in
invalid sql
-----------------------------------------------------------------------------
Key: HHH-5063
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063
Project: Hibernate Core
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.5.0-Final
Reporter: Shawn Clowater
Assignee: Gail Badner
Fix For: 3.5.2, 3.6
Attachments: HHH-5063-testcase.patch
I have a criteria query that is using an AliasToBeanTransformer that I'm using to
selectively populate some of the properties. It appears that the transformer requires the
alias values to match the properties of your bean so that it can call the setters via
reflection.
The code snippet is similar to the following
return (List<DataProvider>) session.createCriteria(DataProvider.class)
.setProjection(Projections.projectionList()
.add(Projections.property("dataProviderId),
"dataProviderId")
.add(Projections.property("uuid"), "uuid")
.add(Projections.property("name"), "name")
.add(Projections.property("dataProviderGroup"),
"dataProviderGroup")
.add(Projections.property("verifiedFlg"),
"verifiedFlg")
)
.setResultTransformer(new
AliasToBeanResultTransformer(DataProvider.class))
.addOrder(Order.asc("name"))
.list();
And is resulting in the following SQL
select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER
this_ order by y2_ asc
I can assure you that my column names are not y0_, etc.
This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If
I don't specify the alias or even change the value then it will produce a valid query
it just won't populate by bean correctly.
i.e. if I append anything to the end of the first alias (i.e. "hi") results
in:
select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from
DATA_PROVIDER this_ order by y2_ asc
--
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
5296
days inactive
5336
days old
hibernate-issues@lists.jboss.org
12 comments
4 participants
participants (4)
-
Gail Badner (JIRA) -
Shawn Clowater (JIRA)
-
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)