Jo�o Mota wrote:
->Using Pb with ODMG Question:
When you use the PB methods with the ODMG broker, the query includes the objects touched by the current transaction?
All queries, PB and OQL queries always are executed against the database.
If an object returned by a query is in the cache already, the cached instance is returned.
So if an object is registered to a tx and then selected by a query, then the same instance is returned by the query.
If not this could lead to problems with locks if the cache is cleared (see
thread with title: Multiple reads within the same transaction). We are
currently doing a second query for every object using the TransactionImpl
method getObjectByIdentity to avoid this problem.
Yup, emtying the cache in the middle of a tx will have an impact on later queries. I'll have a look at the other thread...
->Question About Locks and Reference Update:
When does OJB updates the references to the objects (by reference, I mean the object and the integer that references the id of the object)? The problems im having are best explained by the following example:
Lets say I have an object A that has references to B, C and D
And within a transaction I do:
A xptoA = new A(); lockWrite(xptoA) ; xptoA.setB(xptoB); xptoA.setC(xptoC); xptoA.setD(xptoD);
When commit is done all the references are updated except for the reference to xptoB and so I get an exception because that field in the DB cannot be null.
Then I changed the order of the instructions to: A xptoA = new A();
xptoA.setB(xptoB);
lockWrite(xptoA) ;
xptoA.setC(xptoC);
xptoA.setD(xptoD);
and now all the references are updated.
What I am trying to understand is the difference between B, C and D, so I can understand why this happens.
Hmm, without knowing your real sourcecode, the persistent classes and their mapping, any answer would be guesswork...
-> Question About Firebird Does OJB supports the FireBird DB and the construction of the plataform profile for FireBird is just straightforward or are there any known issues?
As you can see by the enormous list of PlatFormImpls that we already have, it's quite straightforward to adapt OJB to other platforms.
We even provide support for MsAccess! which differs a lot from "normal" RDBMS.
I don't know of any reasons, why FireBird should cause problems.
cheers, Thomas
------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
