You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by "Robert S. Sfeir" <ro...@codepuccino.com> on 2004/06/22 02:08:17 UTC
Escape changes?
Can't remember who was looking at that. Are the ESCAPE char changes made,
or not yet. Since someone else has their hands in it, I'll wait and will be
glad to test again when you have it. Right now with latest CVS error still
happens.
R
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
On 6/25/04 11:19 AM, "Armin Waibel" <ar...@apache.org> wrote:
> And as Martin Kalen mentioned the BlobTest fails because in test schema
> the wrong column type was used (or Torque use the wrong).
>
> So finally we have 405:1:4
>
> Do all sql query pass generated by Torque?
> Because stack shows "[ERROR: relation "ref_animal" does not exist]".
As far as I can tell yes. I've listed the only exceptions I got. The other
tests pass with no errors.
R
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by Armin Waibel <ar...@apache.org>.
And as Martin Kalen mentioned the BlobTest fails because in test schema
the wrong column type was used (or Torque use the wrong).
So finally we have 405:1:4
Do all sql query pass generated by Torque?
Because stack shows "[ERROR: relation "ref_animal" does not exist]".
Armin
Jakob Braeuchi wrote:
> hi robert,
>
> at least the escape test no longer fails ;)
>
> jakob
>
> Robert S. Sfeir wrote:
>
>> Thanks Tom,
>>
>> Here is the result of the changes:
>>
>> junit-no-compile-no-prepare:
>> [junit] Running org.apache.ojb.broker.AllTests
>> [junit] Tests run: 405, Failures: 1, Errors: 5, Time elapsed:
>> 90.808 sec
>>
>>
>> [junit] TEST org.apache.ojb.broker.AllTests FAILED
>> [junit] Running org.apache.ojb.odmg.AllTests
>> [junit] [BOOT] INFO: Loading OJB's properties from file
>> file:/Users/robert/Documents/Projects/db-ojb/target/test/ojb/OJB.properties
>>
>> [junit] [BOOT] INFO: No value for key 'InterceptorClass'
>> [junit] Tests run: 198, Failures: 0, Errors: 0, Time elapsed:
>> 24.358 sec
>>
>>
>> [junit] Running org.apache.ojb.soda.AllTests
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.566 sec
>>
>>
>> [junit] Running org.apache.ojb.otm.AllTests
>> [junit] Tests run: 79, Failures: 0, Errors: 0, Time elapsed:
>> 18.504 sec
>>
>> Failure is:
>> check size expected:<0> but was:<2>
>>
>> junit.framework.AssertionFailedError: check size expected:<0> but
>> was:<2> at
>> org.apache.ojb.broker.QueryTest.testReportPathExpressionForExtents2(QueryTes
>>
>> t.java:1179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
>>
>> ) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
>>
>> .java:25)
>> 0.032
>>
>> Error 1:
>> QL failure while insert object data for class
>> org.apache.ojb.broker.BlobTest$ObjectWithBlob, PK of the given object
>> is [
>> id=1], object was org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246,
>> exception message is [Unknown Types value.]
>>
>> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
>> insert object data for class
>> org.apache.ojb.broker.BlobTest$ObjectWithBlob,
>> PK of the given object is [ id=1], object was
>> org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246, exception
>> message is
>> [Unknown Types value.] at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:243) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
>>
>> Impl.java:1625) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:1542) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:705) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:174) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:174) at
>> org.apache.ojb.broker.BlobTest.testBlobInsertion(BlobTest.java:68) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
>>
>> ) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
>>
>> .java:25)Caused by: org.postgresql.util.PSQLException: Unknown Types
>> value.
>> at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
>>
>> .java:1698) at
>> org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement
>>
>> .java:1370) at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
>>
>> .java:1704) at
>> org.apache.ojb.broker.platforms.PlatformDefaultImpl.setObjectForStatement(Pl
>>
>> atformDefaultImpl.java:227) at
>> org.apache.ojb.broker.platforms.PlatformPostgreSQLImpl.setObjectForStatement
>>
>> (PlatformPostgreSQLImpl.java:42) at
>> org.apache.ojb.broker.accesslayer.StatementManager.bindInsert(StatementManag
>>
>> er.java:449) at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:194) ... 22 more
>>
>> Error 2:
>> SQL failure while insert object data for class
>> org.apache.ojb.broker.Article, PK of the given object is [
>> articleId=88940],
>> object was ---- Article No: 88940 Description: repeated Article
>> ProductGroupId: 1 ProductGroupName: null stock: 0 price: 0.0
>> stock-value 0.0
>> , exception message is [ERROR: duplicate key violates unique constraint
>> "artikel_pkey" ]
>>
>> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
>> insert object data for class org.apache.ojb.broker.Article, PK of the
>> given
>> object is [ articleId=88940], object was ----Article No:
>> 88940Description:
>> repeated ArticleProductGroupId: 1ProductGroupName: nullstock: 0price:
>> 0.0stock-value 0.0, exception message is [ERROR: duplicate key violates
>> unique constraint "artikel_pkey"] at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:243) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
>>
>> Impl.java:1625) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:1542) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:1493) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:180) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:180) at
>> org.apache.ojb.broker.KeyConstraintViolationTest.testKeyViolation(KeyConstra
>>
>> intViolationTest.java:50) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
>>
>> ) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
>>
>> .java:25)Caused by: org.postgresql.util.PSQLException: ERROR:
>> duplicate key
>> violates unique constraint "artikel_pkey" at
>> org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
>>
>> at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
>> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
>> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
>>
>> ava:517) at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
>>
>> ava:50) at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
>>
>> ment.java:273) at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:198) ... 22 more
>>
>> The other errors are:
>> SQL failure while insert object data for class
>> org.apache.ojb.broker.ReferenceTest$Bird, PK of the given object is [
>> id=4],
>> object was org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception
>> message is [ERROR: relation "ref_animal" does not exist ]
>>
>> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
>> insert object data for class org.apache.ojb.broker.ReferenceTest$Bird,
>> PK of
>> the given object is [ id=4], object was
>> org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception message is
>> [ERROR: relation "ref_animal" does not exist] at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:243) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
>>
>> Impl.java:1625) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:1542) at
>> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
>>
>> .java:705) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:174) at
>> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
>>
>> stenceBroker.java:174) at
>> org.apache.ojb.broker.ReferenceTest.testAbstractReferenceStore(ReferenceTest
>>
>> .java:654) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
>>
>> ) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
>>
>> .java:25)Caused by: org.postgresql.util.PSQLException: ERROR: relation
>> "ref_animal" does not exist at
>> org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
>>
>> at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
>> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
>> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
>>
>> ava:517) at
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
>>
>> ava:50) at
>> org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
>>
>> ment.java:273) at
>> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
>>
>> l.java:198) ... 22 more
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
On 6/25/04 11:05 AM, "Jakob Braeuchi" <jb...@gmx.ch> wrote:
> hi robert,
>
> at least the escape test no longer fails ;)
>
> jakob
Hahaha yeah you're right and that's great!
R
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
hi robert,
at least the escape test no longer fails ;)
jakob
Robert S. Sfeir wrote:
> Thanks Tom,
>
> Here is the result of the changes:
>
> junit-no-compile-no-prepare:
> [junit] Running org.apache.ojb.broker.AllTests
> [junit] Tests run: 405, Failures: 1, Errors: 5, Time elapsed: 90.808 sec
>
>
> [junit] TEST org.apache.ojb.broker.AllTests FAILED
> [junit] Running org.apache.ojb.odmg.AllTests
> [junit] [BOOT] INFO: Loading OJB's properties from file
> file:/Users/robert/Documents/Projects/db-ojb/target/test/ojb/OJB.properties
> [junit] [BOOT] INFO: No value for key 'InterceptorClass'
> [junit] Tests run: 198, Failures: 0, Errors: 0, Time elapsed: 24.358 sec
>
>
> [junit] Running org.apache.ojb.soda.AllTests
> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.566 sec
>
>
> [junit] Running org.apache.ojb.otm.AllTests
> [junit] Tests run: 79, Failures: 0, Errors: 0, Time elapsed: 18.504 sec
>
> Failure is:
> check size expected:<0> but was:<2>
>
> junit.framework.AssertionFailedError: check size expected:<0> but was:<2> at
> org.apache.ojb.broker.QueryTest.testReportPathExpressionForExtents2(QueryTes
> t.java:1179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> ) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
> 0.032
>
> Error 1:
> QL failure while insert object data for class
> org.apache.ojb.broker.BlobTest$ObjectWithBlob, PK of the given object is [
> id=1], object was org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246,
> exception message is [Unknown Types value.]
>
> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
> insert object data for class org.apache.ojb.broker.BlobTest$ObjectWithBlob,
> PK of the given object is [ id=1], object was
> org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246, exception message is
> [Unknown Types value.] at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:243) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
> Impl.java:1625) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:1542) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:705) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:174) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:174) at
> org.apache.ojb.broker.BlobTest.testBlobInsertion(BlobTest.java:68) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> ) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)Caused by: org.postgresql.util.PSQLException: Unknown Types value.
> at
> org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
> .java:1698) at
> org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement
> .java:1370) at
> org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
> .java:1704) at
> org.apache.ojb.broker.platforms.PlatformDefaultImpl.setObjectForStatement(Pl
> atformDefaultImpl.java:227) at
> org.apache.ojb.broker.platforms.PlatformPostgreSQLImpl.setObjectForStatement
> (PlatformPostgreSQLImpl.java:42) at
> org.apache.ojb.broker.accesslayer.StatementManager.bindInsert(StatementManag
> er.java:449) at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:194) ... 22 more
>
> Error 2:
> SQL failure while insert object data for class
> org.apache.ojb.broker.Article, PK of the given object is [ articleId=88940],
> object was ---- Article No: 88940 Description: repeated Article
> ProductGroupId: 1 ProductGroupName: null stock: 0 price: 0.0 stock-value 0.0
> , exception message is [ERROR: duplicate key violates unique constraint
> "artikel_pkey" ]
>
> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
> insert object data for class org.apache.ojb.broker.Article, PK of the given
> object is [ articleId=88940], object was ----Article No: 88940Description:
> repeated ArticleProductGroupId: 1ProductGroupName: nullstock: 0price:
> 0.0stock-value 0.0, exception message is [ERROR: duplicate key violates
> unique constraint "artikel_pkey"] at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:243) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
> Impl.java:1625) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:1542) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:1493) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:180) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:180) at
> org.apache.ojb.broker.KeyConstraintViolationTest.testKeyViolation(KeyConstra
> intViolationTest.java:50) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> ) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key
> violates unique constraint "artikel_pkey" at
> org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
> at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
> org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
> ava:517) at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
> ava:50) at
> org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
> ment.java:273) at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:198) ... 22 more
>
> The other errors are:
> SQL failure while insert object data for class
> org.apache.ojb.broker.ReferenceTest$Bird, PK of the given object is [ id=4],
> object was org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception
> message is [ERROR: relation "ref_animal" does not exist ]
>
> org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
> insert object data for class org.apache.ojb.broker.ReferenceTest$Bird, PK of
> the given object is [ id=4], object was
> org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception message is
> [ERROR: relation "ref_animal" does not exist] at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:243) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
> Impl.java:1625) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:1542) at
> org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
> .java:705) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:174) at
> org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
> stenceBroker.java:174) at
> org.apache.ojb.broker.ReferenceTest.testAbstractReferenceStore(ReferenceTest
> .java:654) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> ) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)Caused by: org.postgresql.util.PSQLException: ERROR: relation
> "ref_animal" does not exist at
> org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
> at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
> org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
> org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
> ava:517) at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
> ava:50) at
> org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
> ment.java:273) at
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
> l.java:198) ... 22 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
Thanks Tom,
Here is the result of the changes:
junit-no-compile-no-prepare:
[junit] Running org.apache.ojb.broker.AllTests
[junit] Tests run: 405, Failures: 1, Errors: 5, Time elapsed: 90.808 sec
[junit] TEST org.apache.ojb.broker.AllTests FAILED
[junit] Running org.apache.ojb.odmg.AllTests
[junit] [BOOT] INFO: Loading OJB's properties from file
file:/Users/robert/Documents/Projects/db-ojb/target/test/ojb/OJB.properties
[junit] [BOOT] INFO: No value for key 'InterceptorClass'
[junit] Tests run: 198, Failures: 0, Errors: 0, Time elapsed: 24.358 sec
[junit] Running org.apache.ojb.soda.AllTests
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.566 sec
[junit] Running org.apache.ojb.otm.AllTests
[junit] Tests run: 79, Failures: 0, Errors: 0, Time elapsed: 18.504 sec
Failure is:
check size expected:<0> but was:<2>
junit.framework.AssertionFailedError: check size expected:<0> but was:<2> at
org.apache.ojb.broker.QueryTest.testReportPathExpressionForExtents2(QueryTes
t.java:1179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
0.032
Error 1:
QL failure while insert object data for class
org.apache.ojb.broker.BlobTest$ObjectWithBlob, PK of the given object is [
id=1], object was org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246,
exception message is [Unknown Types value.]
org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
insert object data for class org.apache.ojb.broker.BlobTest$ObjectWithBlob,
PK of the given object is [ id=1], object was
org.apache.ojb.broker.BlobTest$ObjectWithBlob@9d6246, exception message is
[Unknown Types value.] at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:243) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
Impl.java:1625) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:1542) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:705) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:174) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:174) at
org.apache.ojb.broker.BlobTest.testBlobInsertion(BlobTest.java:68) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)Caused by: org.postgresql.util.PSQLException: Unknown Types value.
at
org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
.java:1698) at
org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement
.java:1370) at
org.postgresql.jdbc1.AbstractJdbc1Statement.setObject(AbstractJdbc1Statement
.java:1704) at
org.apache.ojb.broker.platforms.PlatformDefaultImpl.setObjectForStatement(Pl
atformDefaultImpl.java:227) at
org.apache.ojb.broker.platforms.PlatformPostgreSQLImpl.setObjectForStatement
(PlatformPostgreSQLImpl.java:42) at
org.apache.ojb.broker.accesslayer.StatementManager.bindInsert(StatementManag
er.java:449) at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:194) ... 22 more
Error 2:
SQL failure while insert object data for class
org.apache.ojb.broker.Article, PK of the given object is [ articleId=88940],
object was ---- Article No: 88940 Description: repeated Article
ProductGroupId: 1 ProductGroupName: null stock: 0 price: 0.0 stock-value 0.0
, exception message is [ERROR: duplicate key violates unique constraint
"artikel_pkey" ]
org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
insert object data for class org.apache.ojb.broker.Article, PK of the given
object is [ articleId=88940], object was ----Article No: 88940Description:
repeated ArticleProductGroupId: 1ProductGroupName: nullstock: 0price:
0.0stock-value 0.0, exception message is [ERROR: duplicate key violates
unique constraint "artikel_pkey"] at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:243) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
Impl.java:1625) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:1542) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:1493) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:180) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:180) at
org.apache.ojb.broker.KeyConstraintViolationTest.testKeyViolation(KeyConstra
intViolationTest.java:50) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key
violates unique constraint "artikel_pkey" at
org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
ava:517) at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
ava:50) at
org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
ment.java:273) at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:198) ... 22 more
The other errors are:
SQL failure while insert object data for class
org.apache.ojb.broker.ReferenceTest$Bird, PK of the given object is [ id=4],
object was org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception
message is [ERROR: relation "ref_animal" does not exist ]
org.apache.ojb.broker.PersistenceBrokerSQLException: SQL failure while
insert object data for class org.apache.ojb.broker.ReferenceTest$Bird, PK of
the given object is [ id=4], object was
org.apache.ojb.broker.ReferenceTest$Bird@2966a5, exception message is
[ERROR: relation "ref_animal" does not exist] at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:243) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBroker
Impl.java:1625) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:1542) at
org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl
.java:705) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:174) at
org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersi
stenceBroker.java:174) at
org.apache.ojb.broker.ReferenceTest.testAbstractReferenceStore(ReferenceTest
.java:654) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)Caused by: org.postgresql.util.PSQLException: ERROR: relation
"ref_animal" does not exist at
org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139)
at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) at
org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at
org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at
org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j
ava:517) at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j
ava:50) at
org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1State
ment.java:273) at
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImp
l.java:198) ... 22 more
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by Thomas Dudziak <to...@first.fhg.de>.
Robert S. Sfeir wrote:
>Looks like tests are screwed up...
>
>
Ups, my fault. I removed the jdo tutorial stuff from the tests, but
apparently forgot to remove the jdo entity usage from repository.xml.
Will fix this right away.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
Looks like tests are screwed up...
I get this some 417 times :-)
Can't read repository file 'repository.xml'
org.apache.ojb.broker.metadata.MetadataException: Can't read repository file
'repository.xml' at
org.apache.ojb.broker.metadata.MetadataManager.init(MetadataManager.java:159
) at
org.apache.ojb.broker.metadata.MetadataManager.<init>(MetadataManager.java:1
38) at
org.apache.ojb.broker.metadata.MetadataManager.getInstance(MetadataManager.j
ava:172) at
org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.getDefaultKey(Pe
rsistenceBrokerFactoryBaseImpl.java:75) at
org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersisten
ceBroker(PersistenceBrokerFactoryBaseImpl.java:157) at
org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Pers
istenceBrokerFactory.java:65) at
org.apache.ojb.junit.PBTestCase.setUp(PBTestCase.java:29)Caused by:
org.xml.sax.SAXParseException: Reference to undefined entity "&jdo;". at
org.apache.crimson.parser.Parser2.fatal(Parser2.java:3339) at
org.apache.crimson.parser.Parser2.fatal(Parser2.java:3333) at
org.apache.crimson.parser.Parser2.expandEntityInContent(Parser2.java:2660)
at
org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.java:2569)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1980) at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1654) at
org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:634) at
org.apache.crimson.parser.Parser2.parse(Parser2.java:333) at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at
org.apache.ojb.broker.metadata.RepositoryPersistor.readMetadataFromXML(Repos
itoryPersistor.java:310) at
org.apache.ojb.broker.metadata.RepositoryPersistor.buildRepository(Repositor
yPersistor.java:265) at
org.apache.ojb.broker.metadata.RepositoryPersistor.readDescriptorRepository(
RepositoryPersistor.java:177) at
org.apache.ojb.broker.metadata.MetadataManager.init(MetadataManager.java:148
) ... 17 more
On 6/25/04 9:16 AM, "Jakob Braeuchi" <jb...@gmx.ch> wrote:
> hi robert,
>
> i modified the platform for postgresql so it does not use the ESCAPE clause if
> the escape-character is '\' . please verify.
>
> i implemented the platform-dependen escaping long time ago, and i simply
> forgot
> it. i think i'm getting old ;)
>
> jakob
>
> Robert S. Sfeir wrote:
>>
>>
>> On 6/22/04 2:05 AM, "Jakob Braeuchi" <jb...@gmx.ch> wrote:
>>
>>
>>> hi robert,
>>>
>>> i'm not sure whether we should change the escape character in LikeCriteria,
>>> i think '\' is widely accepted. imo the best would be to decide per platform
>>> whether to include the ESCAPE clause in the sql if it matches the default of
>>> the dbms or to double-escape it.
>>>
>>> but for 1.0 i prefer to adapt the failing testcase in class QueryTest and to
>>> use another character there. there is already another testcase using '|' as
>>> escape.
>>
>>
>> I agree to make the test case pass, we should document it however so users
>> know what the issue might be.
>>
>> R
>>
>>
>>> jakob
>>>
>>>
>>>> Can't remember who was looking at that. Are the ESCAPE char changes made,
>>>> or not yet. Since someone else has their hands in it, I'll wait and will
>>>> be
>>>> glad to test again when you have it. Right now with latest CVS error
>>>> still
>>>> happens.
>>>>
>>>> R
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
hi robert,
i modified the platform for postgresql so it does not use the ESCAPE clause if
the escape-character is '\' . please verify.
i implemented the platform-dependen escaping long time ago, and i simply forgot
it. i think i'm getting old ;)
jakob
Robert S. Sfeir wrote:
>
>
> On 6/22/04 2:05 AM, "Jakob Braeuchi" <jb...@gmx.ch> wrote:
>
>
>>hi robert,
>>
>>i'm not sure whether we should change the escape character in LikeCriteria,
>>i think '\' is widely accepted. imo the best would be to decide per platform
>>whether to include the ESCAPE clause in the sql if it matches the default of
>>the dbms or to double-escape it.
>>
>>but for 1.0 i prefer to adapt the failing testcase in class QueryTest and to
>>use another character there. there is already another testcase using '|' as
>>escape.
>
>
> I agree to make the test case pass, we should document it however so users
> know what the issue might be.
>
> R
>
>
>>jakob
>>
>>
>>>Can't remember who was looking at that. Are the ESCAPE char changes made,
>>>or not yet. Since someone else has their hands in it, I'll wait and will
>>>be
>>>glad to test again when you have it. Right now with latest CVS error
>>>still
>>>happens.
>>>
>>>R
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>>For additional commands, e-mail: ojb-dev-help@db.apache.org
>>>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
On 6/22/04 2:05 AM, "Jakob Braeuchi" <jb...@gmx.ch> wrote:
> hi robert,
>
> i'm not sure whether we should change the escape character in LikeCriteria,
> i think '\' is widely accepted. imo the best would be to decide per platform
> whether to include the ESCAPE clause in the sql if it matches the default of
> the dbms or to double-escape it.
>
> but for 1.0 i prefer to adapt the failing testcase in class QueryTest and to
> use another character there. there is already another testcase using '|' as
> escape.
I agree to make the test case pass, we should document it however so users
know what the issue might be.
R
>
> jakob
>
>> Can't remember who was looking at that. Are the ESCAPE char changes made,
>> or not yet. Since someone else has their hands in it, I'll wait and will
>> be
>> glad to test again when you have it. Right now with latest CVS error
>> still
>> happens.
>>
>> R
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Escape changes?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
hi robert,
i'm not sure whether we should change the escape character in LikeCriteria,
i think '\' is widely accepted. imo the best would be to decide per platform
whether to include the ESCAPE clause in the sql if it matches the default of
the dbms or to double-escape it.
but for 1.0 i prefer to adapt the failing testcase in class QueryTest and to
use another character there. there is already another testcase using '|' as
escape.
jakob
> Can't remember who was looking at that. Are the ESCAPE char changes made,
> or not yet. Since someone else has their hands in it, I'll wait and will
> be
> glad to test again when you have it. Right now with latest CVS error
> still
> happens.
>
> R
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
--
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org