I wonder, why do you clear the cache prior to storing the objects ?
And you need transactions around the store call.
Tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Thomas,
When table A is defined, the primary key is not defined with an
autogenerated sequence.
CREATE TABLE A (
A_ID INTEGER NOT NULL,
...
Hence in repository.xml, I declare the PK for A as such:
However, for table B, the PK is defined with a sequence:
CREATE TABLE B (
On 12/19/05, Vamsi Atluri <[EMAIL PROTECTED]> wrote:
> CREATE TABLE A (
> A_ID INTEGER NOT NULL,
> B_ID INTEGER,
> X_ID INTEGER,
> Y_ID INTEGER,
> A_NAME VARCHAR (40),
> CONSTRAINT A_PK PRIMARY KEY (A_ID),
> CONSTRAINT A_FK1 FOREIGN KEY (B_ID
Hello all,
I am running into a strange update issue using OJBs. I am currently using
OJB 1.0.1. My DB setup is as follows:
TABLE A:
CREATE TABLE A (
A_ID INTEGER NOT NULL,
B_ID INTEGER,
X_ID INTEGER,
Y_ID INTEGER,
A_NAME VARCHAR (40),
CONS
