On 2015-02-18 16:07, Stefan Thieme wrote:
(resend as text mail)
Dear Julian,
I have retried the test case (curl5) for the error I got when inserting a
previously deleted node on an Oracle 12c EE database.
I do get the same java.sql.SQLIntegrityConstraintViolation as initially
described for Oracle 11g.
See below for the table description / constraint on Oracle 12c.
Is there a way we could handle this Exception more gracefully, e.g. by throwing
a DocumentStoreException ?
Again, that exception is not supposed to occur.
For the earlier questions:
a) workaround FETCH FIRST as Oracle 11g2 needsRowNumSubquery.
Oracle 12c implicitly uses the same workaround internally by Query
Transformation of FETCH FIRST.
http://oracle-base.com/articles/12c/row-limiting-clause-for-top-n-queries-12cr1.php#query-transformation
This patch would allow to support both Oracle 12c and Oracle 11g2 databases.
For me Oracle 12c is still not a common sight, though undeniable it is the
future.
I can basically live with my small patch on top of OAK-Trunk.
Understood. I'd like to avoid too many special cases; they make testing
and debugging a pain.
b) MAX_ID_VALUE=";" in NodeDocument triggers a SQL Error on Oracle DB,
changing to MAX_ID_VALUE="a" as in ClusterNodeInfoDocument.
I understand that ";" is an ASCII char just above digits 0-9, IMHO even ":"
would suffice for this purpose.
Can someone explain the reasoning behind MAX_ID_VALUE="a" in
ClusterNodeInfoDocument for my own curiosity ?
Marcel?
BTW, I can not reproduce the SQL Error I got initially, which was probably
introduced by a couple of conflicting patches.
> c) add Oak-RDB to server in oak-run Main
adding rdbjdbcuri, rdbjdbcuser and rdbjdbcpassword as OptionalArgs
This has been solved by your update in OAK 1.1.6, thanks!
Kind regards,
Stefan
Best regards, Julian
