db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <guillaume.no...@deliasystems.com>
Subject Bug in batch mode
Date Thu, 05 Feb 2004 18:16:55 GMT
Because of a problem i have using collections,
i can not directly use a store on my object
to save it in the database. I need to perform
first a delete and then a store (as ojb does not
delete old objects from collections, and that i
think is another bug...).
The problem arise when i want to use batch mode.

Let's examine the following code:
	broker.delete(a);
	broker.store(a);
It should leads to the following sql statements:
	DELETE FROM A WHERE ...
	SELECT FROM A WHERE ...   // materializing
	INSERT INTO A

The problem arise in batch mode:
	* the delete statement is kept in memory
	* the select is done and returns a row
	* so an update is send to the database and fails

Regards

Guillaume


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message