Re: [Hibernate] Possible bug in criteria query

2004-10-04 Thread Gavin King
You use createCriteria() to create a join in criteria API. no implicit joins. Ugo Cei wrote: Hi people, given that the following query works as expected: List results = session.find("from it.cbim.sipp.model.Allevamento a" + " where a.indirizzo.comune.provincia.sigla = ?", "PG", Hibernat

[Hibernate] Possible bug in criteria query

2004-10-04 Thread Ugo Cei
Hi people, given that the following query works as expected: List results = session.find("from it.cbim.sipp.model.Allevamento a" + " where a.indirizzo.comune.provincia.sigla = ?", "PG", Hibernate.STRING); I would expect this other query to work as well: Criteria criteria = session

Re: [Hibernate] Possible bug with

2003-01-17 Thread Mark Woon
[EMAIL PROTECTED] wrote: I mean, your column names differ by just the first three chars. Have a look at your mapping. Your patch works by trimming characters from the start, to get it down to the 20 char limit (I changed this to 15, for the benefit of db2). Just try changing your mapping, and see

Re: [Hibernate] Possible bug with

2003-01-16 Thread Gavin . King
<[EMAIL PROTECTED]> To: Sent by:cc: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: [Hibernate] Po

Re: [Hibernate] Possible bug with

2003-01-16 Thread Mark Woon
[EMAIL PROTECTED] wrote: I think it might possibly be to do with your patch for long column names. Try choosing much shorter column names and see what happens. (they are distinguished only by the first three characters). Really? If so, that's a really bad thing. We can't be expecting people

Re: [Hibernate] Possible bug with

2003-01-16 Thread Gavin . King
I think it might possibly be to do with your patch for long column names. Try choosing much shorter column names and see what happens. (they are distinguished only by the first three characters). ** Any personal or sensitive in

[Hibernate] Possible bug with

2003-01-16 Thread Mark Woon
I'm getting some pretty weird behavior with component. Here's my mapping:

RE: [Hibernate] Possible Bug in HQL

2002-12-27 Thread Sven Welte
[snip] > On the other hand, your proposal is no good either, since > it does not return green Foos with bar=null. So it seems > to me like both are imperfect, but existing functionality > is better, because we can force what we mean by adding > "distinct". Ok, I'm happy with the use of "distinct".

RE: [Hibernate] Possible Bug in HQL

2002-12-27 Thread Gavin King
> Here is a query in HQL: > SELECT foo FROM foo IN CLASS Foo > WHERE foo.color='green' AND (foo.bar=? OR foo.bar.someValue='happy') > [snip] > The generated SQL-Code produces the cartesian product between > Foo and Bar: SELECT ... FROM Foo foo, Bar sim0 WHERE > (foo.color='green')AND((foo.barId

[Hibernate] Possible Bug in HQL

2002-12-27 Thread Sven Welte
Ok, here are some tables. CREATE TABLE Foo ( id int PRIMARY KEY, color VARCHAR, barId int, FOREIGN KEY (barId) REFERENCES Bar ) CREATE TABLE Bar ( id int PRIMARY KEY, someValue VARCHAR ) In the mapping there is a association between Foo and Bar. Here is a query in HQL: SELECT foo F

[Hibernate] Possible Bug

2002-12-15 Thread Riddick, Chris
Apologies if this isn't the most suitable channel for bug reports, but... In class... cirrus.hibernate.transaction.WebSphereTransactionManagerLookup I believe the statement... Class.forName("com.ibm.ejcs.jts.jta.JTSXA") should actually be Class.forName("com.ibm.ejs.jts.jta.JTSXA") That works fo