Bernd Ingrid Laengerich wrote:
OK, I played around a little bit and overwrote the afterStore
method (empty implementation, however it never gets called!?
What am I missing? I placed a breakpoint in my code, but it
never reaches it.
OK, searching around a little bit, I found in
Längerich wrote:
Bernd Ingrid Laengerich wrote:
OK, I played around a little bit and overwrote the afterStore
method (empty implementation, however it never gets called!? What
am I missing? I placed a breakpoint in my code, but it never
reaches it.
OK, searching around a little bit, I found
Hi Bernd,
Längerich wrote:
Hi,
I have some problems with OJB (PB-API) and the sequence manager. I
derived a new sequence manager from the shipped HighLowImpl, that
checks for every grab size with
SequenceManagerHelper.getMaxForExtent() for the max id of the field.
This works fine with data
Hi Armin,
thanks again for your response.
Armin wrote:
Längerich wrote:
Is it sufficient/possible to overwrite the afterStore()
method of the
sequence manager?
Yep it's possible. Assume you want to lookup the
HLSequence-object for
the current used (fixed) field and invalidate the
Hi,
I have some problems with OJB (PB-API) and the sequence manager. I derived a
new sequence manager from the shipped HighLowImpl, that checks for every grab
size with SequenceManagerHelper.getMaxForExtent() for the max id of the field.
This works fine with data added externally, but I have a
Hi John,
sorry for the hassle. Between 1.0.3 and 1.0.4 we have to change Identity
handling but I forget completely to update docs.
More details here
http://mail-archives.apache.org/mod_mbox/db-ojb-user/200602.mbox/[EMAIL
PROTECTED]
or
I am trying to use the following approach to get a unique sequence value
without actually persisting an object into the table associated with
the sequence. (I really only want the unique sequence of values. I.e. if
the DB provided an Oracle style sequence, I'd probably just do a SQL
nextval()
Hello there,
we use in one case Informix and the
org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImpl as the sequence
manager.
First it seemed good but then we must realize that we can't create a new record,
if we didn't create a record in the rdbms before using OJB.
So if we want to
?
At the moment I have no ideas because I don't know how this sequence manager
works.
Any suggestions are welcome! :)
Have a look in method
SequenceManagerHighLowImpl#lookupStoreSequence(PersistenceBroker broker,
FieldDescriptor field, String seqName)
this method is called to store/lookup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Armin,
Have a look in method
SequenceManagerHighLowImpl#lookupStoreSequence(PersistenceBroker broker,
FieldDescriptor field, String seqName)
this method is called to store/lookup a HighLowSequence instance.
OJB first lookup
= 'deprecatedColumn'
regards,
Armin
Frank Renaers wrote:
Hi,
We are using the SequenceManagerHighLowImpl implementation. (OJB1.0.0).
We are using the spy driver to check the generated sql.
The log contains the following sql statement :
UPDATE OJB_HL_SEQ SET MAX_KEY='513',GRAB_SIZE='1',VERSION
When using two instances of ojb on different data sets, but using the same
table for SequenceManagerHighLowImpl, i ran into an optimistic lock error.
I took a look at the code, and i see there were 5 retries to test for
achieving
the select / store process.
My question is: as the HighLowSequence
Hi Guillaume,
Guillaume Nodet wrote:
When using two instances of ojb on different data sets, but using the same
table for SequenceManagerHighLowImpl, i ran into an optimistic lock error.
I took a look at the code, and i see there were 5 retries to test for
achieving
the select / store process
?
-Message d'origine-
De : Armin Waibel [mailto:[EMAIL PROTECTED]
Envoye : vendredi 30 janvier 2004 10:56
A : OJB Users List
Objet : Re: Optimistic locking error with SequenceManagerHighLowImpl
Hi Guillaume,
Guillaume Nodet wrote:
When using two instances of ojb on different data sets
: Armin Waibel [mailto:[EMAIL PROTECTED]
Envoye : vendredi 30 janvier 2004 10:56
A : OJB Users List
Objet : Re: Optimistic locking error with SequenceManagerHighLowImpl
Hi Guillaume,
Guillaume Nodet wrote:
When using two instances of ojb on different data sets, but using the same
table
a,
Just to check: are you saying that it is possible to use the latest JDBC
driver (that comes with Oracle 9.x) with Oracle 8.1.7? Do you have a
link to more information about possible issues doing this?
Thanks,
I'm using the classes12-g.zip (i'm still on JDK1.3) JDBC Driver for Oracle
9.2
Hi,
strange!
Could you post a test case or add a test to one of
the existing test cases to reproduce
your problem?
Yes it's strange, I noticed a couple of thing ... that could be wrong:
First of all, the problem seems the storing of the HighLowSequence object.
The maxKey attribute is a 'long'
: SequenceManagerHighLowImpl: trouble on rc3
Hi,
Do you use the repository_internal.xml
shipped with rc3?
Do you update OJB_HL_SEQ table?
more info see release notes shipped with rc3.
Yes, I did. I updated the OJB.properties file too for matching the new
broker packaging
Hi all,
currently I checked in a new version of SequenceManagerHighLowImpl.
Now the implementation use otimistic locking to avoid id generation
problems when OJB was used in different JVM with same database.
To enable this behaviour the OJB_HL_SEQ table was enhanced.
The table needs
19 matches
Mail list logo
