[At 19.12.2005 01:39, Gabriel Genellina kindly sent the following
quotation.]
Gabriel, I appreciate you also reviewed my code.
>> def manage_afterAdd(self, item, container): if item is self:
>> self.db = getattr(self,MY_CONNECTION_ID)._v_database_connection
>
> Keeping a _v_ attribute is *not*
At Saturday 17/12/2005 09:31, Vlada Macek wrote:
in ZopeBook I read that Zope's transaction are tied to SQL backend's
ones. I do not know whether this applies to ZSQL methods only, but I
do not expect it. I got this table:
def manage_afterAdd(self, item, container):
if item is se
[At 17.12.2005 15:37, Vlada Macek kindly sent the following quotation.]
>What is serious here is the first connection with my statement is not
>committed. I think this is a bug, probably in ZPsycopgDA.
>
>
Downgrading psycopg to 1.1.18 solved my problem with pending
transactions. I'm going to po
[At 17.12.2005 15:17, Tino Wildenhain kindly sent the following quotation.]
>>In the meanwhile I also discovered that when I put my 'insert into
>>testtable...' to ZSQL method, the behavior is the same -- psql does not
>>see new row, but the sequence is incremented. Now it's strange, isn't?
>>
Am Samstag, den 17.12.2005, 14:20 +0100 schrieb Vlada Macek:
> [At 17.12.2005 13:49, Andreas Jung kindly sent the following quotation.]
>
> > Dealing with transaction is the task of the database adapter and not
> > the ZSQL methods. If you need to deal with transactions yourself you
> > must subcl
[At 17.12.2005 13:49, Andreas Jung kindly sent the following quotation.]
> Dealing with transaction is the task of the database adapter and not
> the ZSQL methods. If you need to deal with transactions yourself you
> must subclass the transaction manager TM and implement the hooks for
> commit and
Forwarded Message
Date: 17. Dezember 2005 13:31:23 +0100
From: Vlada Macek <[EMAIL PROTECTED]>
To: zope@zope.org
Subject: [Zope] SQL transaction uncommited?
Hi,
in ZopeBook I read that Zope's transaction are tied to SQL backend's
ones. I do not k
Hi,
in ZopeBook I read that Zope's transaction are tied to SQL backend's
ones. I do not know whether this applies to ZSQL methods only, but I
do not expect it. I got this table:
CREATE TABLE testtable
(
id serial, -- uses its own sequence
n int4
);
I use PostgreSQL a
