Hi Armin,
thanks for help.
I guess, you don't mean 1.0.5 by next major version, maybe 1.1? Is there
already a date for the release of the next major version available?
Best regards,
Abid
Armin Waibel schrieb:
Hi Abid,
Abid Hussain wrote:
Hi everybody,
I've a table with quite a lot of
Hi Abid,
Abid Hussain wrote:
Hi everybody,
I've a table with quite a lot of columns. When using
broker.update(object) all columns are updated. Is there a way to only
update the columns which actually changed? I'm looking for something
like UPDATE MyTable SET MyTableColumn = new_value WHERE
Hi everybody,
I've a table with quite a lot of columns. When using
broker.update(object) all columns are updated. Is there a way to only
update the columns which actually changed? I'm looking for something
like UPDATE MyTable SET MyTableColumn = new_value WHERE ID=xxx.
Anyone got an idea?
On 12/27/05, Vamsi Atluri [EMAIL PROTECTED] wrote:
I am currently using ojb 1.0.1. I have a table with several references.
The first time when I insert to this table everything inserts correctly.
The next time, when I need to update this row, I retrieve the reference
from DB, update the
Hello all,
I am currently using ojb 1.0.1. I have a table with several references.
The first time when I insert to this table everything inserts correctly.
The next time, when I need to update this row, I retrieve the reference
from DB, update the values and call broker.store() again. That's when
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:
class-descriptor class=A table=A
field-descriptor name=aId column=A_ID
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]
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, X_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),
Here is my problem:
I've got an object of class A with a collection of objects of class B.
I receive fresh new objects to update from a source that is not ojb.
When i want to update the object of class A the following operations
are performed (let say i have only one B object in the
a
insert into b ... // insert new collection
Can anyone give me a hint the problem ?
-Message d'origine-
De : Guillaume Nodet [mailto:[EMAIL PROTECTED]
Envoye : mardi 3 fevrier 2004 10:12
A : OJB Users List
Objet : Problem updating objects with collections
Here is my
it is not possible to use this method ..No?
-Message d'origine-
De : Mahler Thomas [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 18 juin 2003 16:40
À : 'OJB Users List'
Objet : RE: Updating Objects
Hi Eric,
Is it appropriate to update a persisted object by creating an
new object
with same id
: mercredi 18 juin 2003 16:40
À : 'OJB Users List'
Objet : RE: Updating Objects
Hi Eric,
Is it appropriate to update a persisted object by creating an
new object
with same id as the persisted object and then persisting the
new object?
I don't think this is best practise. But there may
the existence or not
for each object Updated in database via ODMG API before insert it) must be
preferred ?
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 19 juin 2003 11:28
À : OJB Users List
Objet : Re: RE : Updating Objects
Hi
Emmanuel Dupont wrote:
Hi
Is it appropriate to update a persisted object by creating an new object
with same id as the persisted object and then persisting the new object? In
case your curious, it does properly update the database.
Eric
DISCLAIMER: The information contained in this e-mail is, unless otherwise
Hi Eric,
Is it appropriate to update a persisted object by creating an
new object
with same id as the persisted object and then persisting the
new object?
I don't think this is best practise. But there may be reasons to such
things...
At least from an OJB point of view I see no
16 matches
Mail list logo