Laurence Rowe wrote:
>
> tsmiller wrote:
>
I have a bookstore that uses the ZODB as its storage. It uses qooxdoo
as
the client and CherryPy for the server. The server has a
'saveBookById'
routine that works 'most' of the time. However, sometimes the
transaction.
Christian Theune-2 wrote:
>
> On Wed, May 28, 2008 at 07:55:19PM -0700, tsmiller wrote:
>>
>> ZODB list,
>>
>> I have a bookstore that uses the ZODB as its storage. It uses qooxdoo as
>> the client and CherryPy for the server. The server has a 'saveBookById'
>> routine that works 'most' of t
tsmiller wrote at 2008-5-28 19:55 -0700:
> ...
>I have a bookstore that uses the ZODB as its storage. It uses qooxdoo as
>the client and CherryPy for the server. The server has a 'saveBookById'
>routine that works 'most' of the time. However, sometimes the
>transaction.commit() does NOT commit t
On Wed, May 28, 2008 at 07:55:19PM -0700, tsmiller wrote:
>
> ZODB list,
>
> I have a bookstore that uses the ZODB as its storage. It uses qooxdoo as
> the client and CherryPy for the server. The server has a 'saveBookById'
> routine that works 'most' of the time. However, sometimes the
> tran
ZODB list,
I have a bookstore that uses the ZODB as its storage. It uses qooxdoo as
the client and CherryPy for the server. The server has a 'saveBookById'
routine that works 'most' of the time. However, sometimes the
transaction.commit() does NOT commit the changes and when I restart my
serve
