|
> On Thu, Feb 16, 2006 at 10:15:35AM +0100, Ales Smrdel wrote: > > which can > > lead to inconsistencies > > Inconsistencies should be resolved with transactions:> > http://www.postgresql.org/docs/7.4/static/transaction-iso.html > > Oleg. Thanks for the answer (I am using postgres). If I got this rigth, than the values that changed in between reading and final writing won't be affected? Does anybody know if it is possible to use transactions with the selectBy() command or is this possible only with the get() command (selectBy is done with the field, which is unique)? I also use two reads from the database, and one write, 1. read is to create and display the page, after which I loose pointer to the record in question, so I have to make another selectBy and only afterwards the new data is writen. Can this in any way influence the result of transactions? Thanks in advance Ales. P.S. Sorry for ?stupid? questions but I've really never before did anything with databases and after this application probably never will again.------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss |
