Antonio, you've got me there ;-)
I posted my reply a few seconds after yours.
As I said it's not a real bug in my opinion, because if you create an
object instance without PK values a QueryByIdentity doesn't make sense.
The bad design was that OJB assume that the object was "new" and obtain
a ne
Hi Carlos,
it's not a "real bug" more a combination of bad design (Identity obtain
new id's if needed) and wrong usage.
In your example you are using QueryByIdentity and OJB expect that the
object does exists. Internal OJB build an Identity instance using the
specified Client object and use PB#
Hi:
We are trying to fix this problem:
Using QueryByIdentity is the key is set to null, then the sequence manager
is activated. Here is the snapshot of the code:
Client c = new Client();
c.setCli_id(null); /* <--- Set the key to null */
Query query = new QueryByIdentity(c);
Hello to all.
I found a strange behavior in OJB.
Suppose that I have the table client, the value of the field cli_id is
taken from a sequence, the table is in PostgreSQL, cli_id is the
primarykey and is a integer.
if I want to recover a client using QueryByIdentity and getObjectByQuery,
Hello to all.
I found a strange behavior in OJB.
Suppose that I have the table client, the value of the field cli_id is
taken from a sequence, the table is in PostgreSQL, cli_id is the
primarykey and is a integer.
if I want to recover a client using QueryByIdentity and getObjectByQuery,
