[Zope] ODBC and Inserting not committed

[Rob Page]

I suspect that this is related to the fact that the DA has not been
intergrated with the New and Improved transaction control machinery for
ZODB3.  I've asked the question internally -- hopefully we'll have a
response (note I didn't say solution!) later today...

--Rob

> -----Original Message-----
> From: Graham Chiu [mailto:anon_emouse@hotmail.com]
> Sent: Tuesday, July 27, 1999 6:31 AM
> To: zope@zope.org
> Subject: Re: [Zope] ODBC and Inserting not committed
> 
> 
> In article <58M3aDAI0Wn3Ew48@compkarori.co.nz>, Graham Chiu
> <anon_emouse@hotmail.com> writes
> >>Try running Zope in single thread mode ('-t 1' on the z2.py command
> >>line) and see if the problem persists.  If so, then the 
> ODBC driver will
> >>probably need to be 'thunked' which is a pretty trivial 10 
> minute change
> >>to the code.
> >
> >I ran it in single thread mode, and the problem has gone 
> away.  Actually
> >I just found that updates also did not commit before.  Now 
> both commit.
> 
> Oops, spoke too soon.  Changes are now saved between browser sessions,
> but are discarded once Zope2b1 is closed down.
> 
> -------
> Regards,        Graham Chiu
> gchiu<at>compkarori.co.nz
> 
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://www.zope.org/mailman/listinfo/zope
> 
> (To receive general Zope announcements, see:
> http://www.zope.org/mailman/listinfo/zope-announce
> 
> For developer-specific issues, zope-dev@zope.org -
> http://www.zope.org/mailman/listinfo/zope-dev )
>