> >
> > When using %mdat you should not use NullLocker, because you need
locking,
> > otherwise you may get corrupted data, because multiple request can
happen at
> > the same time to the same page.
>
> I apparently don't get it - I thought Postgres didn't need application
> locking because it takes care of the translations itself so NullLocker
> is appropriate. How wrong am I?
>
I know to less about Progres to say anything how Postgres handles this, but
for %mdat you get the problem that one request retrieves the data, modifies
it and before it can write it back, another process requests the data and
modifies it. The second request sees the unmodified data, but should wait
until the first process has written back the data. This is why for %mdat
locking is important. For %udat this isn't such an issue because normaly you
only have one request from one user at a time.
Maybe Postgress or the Apache::Session Postgres drivers does some smart
things about this. I don't know. Any Postgres expert who can shed some light
into this ?
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
