>you already have a pool there. from what is see for
every thread
>you'll have a db connection.
That's what I thought although I had seen schemes where
they were in an
explict pool, one where you 'got' a connection and when
you were
finished you 'put' it back into the pool but I can't
really see how
that helps this situation.
>did the writter add that row at all in the database ? (
did you force
>a commit ? )
I'm not 100% sure I understand you here. I have one
published method
'insert' which writes a row and one, 'browse' which
attempts to read it
- it's the second one which sometimes cannot see the
database row.
Yes I have set 'auto-commit' to false before I do anything
on the
insert and then I explicitly commit the update.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---
|