[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1587?page=c...
]
Etienne Bernard commented on HHH-1587:
--------------------------------------
Hi Diego,
Honestly I don't use PostgreSQL anymore, and this bug is really old. I think it was
solved during the 3.2 development phase. I think you can close it without any problem.
'true' and 'false' as keywords for PostgreSQL
dialect
-----------------------------------------------------
Key: HHH-1587
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1587
Project: Hibernate3
Issue Type: Improvement
Reporter: Etienne Bernard
Assignee: Diego Plentz
Priority: Minor
I'm using the PostgreSQL dialect with hibernate 3.1.
I tried to add a ' where="active=true" ' restriction on my collection
mapping.
Unfortunately, it was incorrectly interpreted as a column name by the query parser :
FROM es.vodafone.tienda.model.Phone AS p JOIN p.activePhonePacks AS pp
WHERE p.active=true
where rewritten as :
select phone0_.id as col_0_0_, activephon1_.id as col_1_0_ from phone phone0_ inner join
phonepack activephon1_ on phone0_.id=activephon1_.phone and
activephon1_.active=activephon1_.true where phone0_.active=true
The solution seems to register "true" and "false" as keywords in the
PostgreSQL dialect :
registerKeyword("true");
registerKeyword("false");
Thanks.
--
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