Re: [Hibernate-devel] Probable bug

[Christian B. <chr...@bl...>]

On 18 Jul (11:14), Gavin_King/Cirrus%CI...@ci... wrote:

> On the other hand, this is the exact area of the code that changed between
> 1.0 and 1.0.1 so his bug report is utterly credible.

Using the CVS snapshot, my test application is broken too:

### QUERY: SELECT addressGroup FROM addressGroup IN CLASS AddressGroup ORDER
BY addressGroup.name

Produces:

finding SELECT addressGroup FROM addressGroup IN CLASS AddressGroup ORDER
BY addressGroup.name 

SELECT addressGroup FROM addressGroup IN CLASS AddressGroup ORDER
BY addressGroup.name

SELECT DISTINCT addressGroup.address_group_id as address_group_id0,
addressGroup.address_group_id as address_group_id1, addressGroup.name as
name0, addressGroup.name as name1 FROM address_groups addressGroup WHERE
1=1   ORDER BY addressGroup.name addressGroup.name

SELECT DISTINCT addressGroup.address_group_id as address_group_id0,
addressGroup.address_group_id as address_group_id1, addressGroup.name as
name0, addressGroup.name as name1 FROM address_groups addressGroup WHERE
1=1   ORDER BY addressGroup.name addressGroup.name

closing session
disconnecting session
class java.sql.SQLException ERROR:  parser: parse error at or near
"addressgroup"


This is simple mapping, just like the reported one but without any
relationships and collections.

Looks like the ORDER BY is broken and the _id0/_id1 stuff is too.


Hibernate 1.0.1:

### QUERY: SELECT addressGroup FROM addressGroup IN CLASS AddressGroup
ORDER BY addressGroup.name

finding SELECT addressGroup FROM addressGroup IN CLASS AddressGroup ORDER
BY addressGroup.name

SELECT addressGroup FROM addressGroup IN CLASS AddressGroup ORDER 
BY addressGroup.name

SELECT DISTINCT addressGroup.address_group_id, addressGroup.name FROM
address_groups addressGroup WHERE 1=1   ORDER BY addressGroup.name

SELECT DISTINCT addressGroup.address_group_id, addressGroup.name FROM
address_groups addressGroup WHERE 1=1   ORDER BY addressGroup.name

HTH

-- 
Christian Bauer
tu...@in...