1. OJB generates the SQL to to the CRUD operations. There is currently no way to replace this with calls to a stored procedure. Your question, however, doesn't really have enough details for me to infer exactly what you want to do.
2. I haven't used it yet, but as I understand there is support for a timestamp attribute in ODMG. OJB will work in a distributed system, and has been designed to do so. Do you mean you have other progs accessing the database other than OJB? If that's what you mean, then you would have to do some extra work to make these play nicely. m > -----Original Message----- > From: Jacob Hookom [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 3:15 PM > To: [EMAIL PROTECTED] > Subject: [GENERAL] Stored Procedures / Distributed Systems > > > 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]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
