Database Query Contains Old Data

M.-A. Lemburg mal at egenix.com
Wed Jun 4 10:30:47 CEST 2008


On 2008-06-03 14:29, James A. Donald wrote:
> On Tue, 03 Jun 2008 12:07:07 +0200, "M.-A. Lemburg" <mal at egenix.com>
> wrote:
>> As others have mentioned, in systems that have long running logical
>> transactions, it's usually best to collect the data until the very
>> end and then apply all changes in one go (and one database
>> transaction).
> 
> I understand you to mean that one should arrange matters so that what
> is a lengthy transaction from the point of view of the user is a short
> transaction from the point of view of the database.

Yes, mainly to avoid database locks.

In a multi-user environment, you will need to add some merge logic
in your application, to prevent conflict errors in the database.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Jun 04 2008)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
2008-07-07: EuroPython 2008, Vilnius, Lithuania            32 days to go

:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::


    eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
     D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
            Registered at Amtsgericht Duesseldorf: HRB 46611



More information about the Python-list mailing list