On Tue, 22 Feb 2005 09:04:01 -0600, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
Ok, any particular reason we explicitly allow the oracle-mode usage to
continue? ;)
No, besides noone have ever complained ,)
I guess it would make sense to have two dialects or ?
/max
-Original Message-
From:
Ok, any particular reason we explicitly allow the oracle-mode usage to
continue? ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Tuesday, February 22, 2005 8:57 AM
To: Steve Ebersole; Gavin King; hibernate-devel@lists.sourcefo
On Tue, 22 Feb 2005 08:57:13 -0600, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
SAP (or at least MAXDB, which it became) has two modes of operation:
normal
and oracle. The oracle mode simulates oracle-style theta syntax; the
normal
mode uses ansi-style joins. Any particular reason we explici
SAP (or at least MAXDB, which it became) has two modes of operation: normal
and oracle. The oracle mode simulates oracle-style theta syntax; the normal
mode uses ansi-style joins. Any particular reason we explicitly use the
oracle mode?
> -Original Message-
> From: [EMAIL PROTECTED]
> [
That should be fine. Tonight I'm going to try to move the testing scenarios
into the main build.xml file, as it doesn't need to be in the nightly
build.xml file.
Also, I've realized that the coverage analysis could be cumulative (across
all test scenarios), would that be more useful than the indi
I suppose we'll see. I've scheduled a build for 1pm EST as well. :)
Also, I've installed MySQL 4.1 on that machine which should help the mysql
configurations pass.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Max Rydahl Andersen
> Sent: Tue
On Tue, 22 Feb 2005 08:05:19 -0500, Joshua Davis <[EMAIL PROTECTED]> wrote:
I'll install MySQL 4.1, which should fix the ast-mysql and classic-mysql
tests.
Did someone already fix the junitinstrument target in build.xml?
I made the instrument task not re-instrument already instrumented classes.
But
I'll install MySQL 4.1, which should fix the ast-mysql and classic-mysql
tests.
Did someone already fix the junitinstrument target in build.xml?
> -Original Message-
> From: Gavin King [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 21, 2005 9:27 PM
> To: Joshua Davis
> Cc: hibernate-
I'll make a decorator for HQLTest that uses the Oracle dialect, it shouldn't
need to actually connect to the DB and it will show the differences in SQL
generation.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Gavin King
> Sent: Tuesday, Februa
On Tue, 22 Feb 2005 21:37:00 +1100, Gavin King <[EMAIL PROTECTED]> wrote:
This makes almost all tests fail with OracleDialect and the new parser.
TimesTen and SAP too
-max
Gavin King wrote:
Ok, well it looks like almost all of the Oracle failures are to do with:
where x in elements(y.collectio
Using OracleDialect (instead of Oracle9Dialect), things seem to
basically work, except, sometimes there is a missing comma in the from
clause. This is 'cos you need commas in theta-style joins where you
would not need them in ANSI-style joins.
This makes almost all tests fail with OracleDialect
Ok, well it looks like almost all of the Oracle failures are to do with:
where x in elements(y.collection)
So we need to fix this one...
--
Gavin King
+61 410 534 454
+1 404 822 8349
callto://gavinking
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://jboss.com
-
or not x = y
seems to not be supported by the second stage of the grammar ... I'm
guessing this is probably easy to fix?
--
Gavin King
+61 410 534 454
+1 404 822 8349
callto://gavinking
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://jboss.com
13 matches
Mail list logo
