hi jacob, 1. ojb creates the sql dynamically and has currently no support for stored procedures. 2. you can use an optimistic locking based on timestamps or a version number. just define locking=true in the field descriptor.
hth jakob > Hi, > > I have a few simple questions dealing with OJB implementation. > > 1. If much of the database functionality is encapsulated in stored > procedures for CRUD methods, are we able to override CRUD methods of an > object or do we have to essentially 're-script' the stored procedure in > java much like the 'tutorial4' specs with listeners? > > 2. If we are potentially dealing with a distributed system, can we set a > 'last modified' in the -user.xml to check the db against the cache or > will this terribly slow down the OJB cache implementation with a per > item check? > > Best Regards, > Jacob > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.386 / Virus Database: 218 - Release Date: 9/9/2002 > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
