A little bit of a non-sequitor here... but I'm wondering whether it is
correct to fix
the issues below in the Merge stuff.
1. I'm wondering where the responsibility lies for making sure that the
entry of an AUTO_PK_SUPPORT is > max of pk. A table may exist before
AUTO_PK_SUPPORT is added.
59563 [SocketListener0-9] INFO org.apache.cayenne.access.QueryLogger
- DELETE FROM AUTO_PK_SUPPORT WHERE TABLE_NAME IN ('Comment')
59626 [SocketListener0-9] INFO org.apache.cayenne.access.QueryLogger
- INSERT INTO AUTO_PK_SUPPORT (TABLE_NAME, NEXT_ID) VALUES ('Comment',
200)
2. I get these (harmless) exceptions when adding a table w/Derby. Is
that intentional?
59376 [SocketListener0-9] INFO com.zylin.payback.app.db.DBManager -
Create Table Comment To DB
59376 [SocketListener0-9] INFO org.apache.cayenne.access.QueryLogger
- CREATE TABLE AUTO_PK_SUPPORT ( TABLE_NAME CHAR(100) NOT NULL,
NEXT_ID BIGINT NOT NULL, PRIMARY KEY(TABLE_NAME))
59548 [SocketListener0-9] INFO org.apache.cayenne.access.QueryLogger
- *** error.
java.sql.SQLException: Table/View 'AUTO_PK_SUPPORT' already exists in
Schema 'APP'.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
-- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
This archive was generated by hypermail 2.0.0 : Fri Aug 22 2008 - 08:18:21 EDT