sen
Sent: Monday, 14 February 2005 10:42 PM
To: Gavin King; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] New SQLQuery interface.
On Mon, 14 Feb 2005 05:39:12 -0600, Gavin King <[EMAIL PROTECTED]>
wrote:
Oh, I did not read the whole thread. No, the order is not controlle
ernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] New SQLQuery interface.
On Mon, 14 Feb 2005 05:06:46 -0600, Gavin King <[EMAIL PROTECTED]>
wrote:
yep.
well - maybe i'm blind, but looking at the
current SQLTest.java (and the underlying impl) it still
looks like its called addXXX
9:58 PM
To: 'hibernate-devel@lists.sourceforge.net'
Subject: Re: [Hibernate] New SQLQuery interface.
Hi,
whatever happend to the stuff discussed in this thread ?
was anything changed or ?
-max
Guys, please review:
org.hibernate.test.sql.SQLQueryTest.testSQLQueryInterface()
It demonstr
Hi,
whatever happend to the stuff discussed in this thread ?
was anything changed or ?
-max
Guys, please review:
org.hibernate.test.sql.SQLQueryTest.testSQLQueryInterface()
It demonstrates the new SQLQuery interface, which will replace the
horrible createSQLQuery() methods.
It for sure looks bet
Here is the error I'm getting:
org.hibernate.MappingException: Error reading resource:
org/hibernate/test/sql/Employment.hbm.xml
at org.hibernate.cfg.Configuration.addResource(Configuration.java:427)
...
Caused by: org.xml.sax.SAXParseException: Attribute "class" is required
and must be spe
I've just updated and I can't find the test. I'll try again. SQLTest
seems to fail becaues of a DTD validation problem as well... maybe my
classpath is incorrect.
Gavin King wrote:
Guys, please review:
org.hibernate.test.sql.SQLQueryTest.testSQLQueryInterface()
It demonstrates the new SQLQuer
On Tue, 25 Jan 2005 12:01:27 +0100, Max Rydahl Andersen
<[EMAIL PROTECTED]> wrote:
addEntity is better than setEntity (which we IM'ed about),
but is "add" the right word/concept for the user ? Would mapEntity,
aliasEntity, bindEntity be better ?
Alternatively we could mimic the DTD and have
s
Hi,
>> It demonstrates the new SQLQuery interface, which will replace the
>> horrible createSQLQuery() methods.
>
> It for sure looks better.
I also like the look of it.
> List l = s.createSQLQuery("select {org.*}, {emp.*}, emp.regionCode from
> organization org left outer join employment emp on
On Tue, 25 Jan 2005 12:17:59 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
Inline
Max Rydahl Andersen wrote:
On Tue, 25 Jan 2005 09:48:20 +1100, Gavin King <[EMAIL PROTECTED]>
wrote:
Then there is the whole sequencing of the resulting Object[] ?
I would rather have addXxx order as signif
I think I forgot to commit my test dir earlier. Try now.
Joshua Davis wrote:
I've just updated and I can't find the test. I'll try again.
SQLTest seems to fail becaues of a DTD validation problem as well...
maybe my classpath is incorrect.
Gavin King wrote:
Guys, please review:
org.hibernate.
Inline
Max Rydahl Andersen wrote:
On Tue, 25 Jan 2005 09:48:20 +1100, Gavin King <[EMAIL PROTECTED]>
wrote:
Then there is the whole sequencing of the resulting Object[] ?
I would rather have addXxx order as significant
If we want to keep the strict ordering scalar-first, entities-last
Why do we
On Tue, 25 Jan 2005 09:48:20 +1100, Gavin King <[EMAIL PROTECTED]> wrote:
Guys, please review:
org.hibernate.test.sql.SQLQueryTest.testSQLQueryInterface()
It demonstrates the new SQLQuery interface, which will replace the
horrible createSQLQuery() methods.
It for sure looks better.
Let me know wh
Guys, please review:
org.hibernate.test.sql.SQLQueryTest.testSQLQueryInterface()
It demonstrates the new SQLQuery interface, which will replace the
horrible createSQLQuery() methods.
Let me know what you think. I'm not 100% sold on it yet.
Thanks,
Gavin
--
Gavin King
+61 410 534 454
+1 404 822 83
13 matches
Mail list logo
