On Nov 8, 2009, at 6:48 AM, James wrote:
>
> On Nov 7, 5:28 pm, Michael Bayer wrote:
>> the most obvious cause would be that two different engines are being
>> used, since sqlite memory databases are local only to a single
>> connection.
>
> Thanks for this pointer Michael!
>
> I tried putting
On Nov 7, 5:28 pm, Michael Bayer wrote:
> the most obvious cause would be that two different engines are being
> used, since sqlite memory databases are local only to a single
> connection.
Thanks for this pointer Michael!
I tried putting extra logging in the _cursor_execute method of
sqlal
On Nov 7, 2009, at 6:06 AM, James wrote:
>
> Can anyone see why a new created table wouldn't be found by
> SQLAlchemy? What more information could I give that would be useful?
>
> This is using sqlalchemy.url = sqlite:///:memory:
the most obvious cause would be that two different engines are be
