On Wed, 28 Jul 2010 15:17:09 +0530 (IST), Faheem Mitha
fah...@email.unc.edu wrote:
Hi,
When calling create_all on a metadata instance after a
session has
alrady been opened causes the create_all to hang, I
assume because
the session is blocking the create_all. Is there
On 7/29/10 17:18 , Faheem Mitha wrote:
Hi Simon,
Thanks. Do you understand why this blocking takes place? I assume by
default create_all tries to make a different connection, and fails for
some reason?
My guess is that it does not fail, but your database is blocking the
create_all statements
On Thu, 29 Jul 2010 15:18:33 + (UTC)
Faheem Mitha fah...@email.unc.edu wrote:
On Thu, 29 Jul 2010 11:36:43 +0100, King Simon-NFHD78
simon.k...@motorola.com wrote:
You can tell meta.create_all() to use the same underlying DB
connection as the session by using the session.connection()
On Wed, 2010-07-28 at 11:33 +, Faheem Mitha wrote:
On Wed, 28 Jul 2010 15:17:09 +0530 (IST), Faheem Mitha fah...@email.unc.edu
wrote:
Hi,
When calling create_all on a metadata instance after a session has
alrady been opened causes the create_all to hang, I assume because
the
On Wed, 2010-07-28 at 17:17 +, Faheem Mitha wrote:
Hi Lance,
On Wed, 28 Jul 2010 06:45:30 -0500, Lance Edgar lance.ed...@gmail.com wrote:
--=-dKyzuPx4woj1H0B5IT48
Content-Type: text/plain; charset=ISO-8859-1
On Wed, 2010-07-28 at 11:33 +, Faheem Mitha wrote:
On Wed, 28 Jul
