the standard SQLAlchemy patterns should work fine here:
- in 0.7, create_engine() will set up a NullPool when using SQLite against a
file. SQLite doesn't really need connection pooling in the usual case.
nothing special is required here on your part.
- when using a Connection, if you're doing
I'm new to sqlalchemy and was looking at a good starting point. I currently
have
an application which has multiple threads at certain parts, some of which need
access to the same sqlite database at the same time. Mostly only one writing
but
sometimes more than one thread will need to write to
I found the problem. I executed a query where I check against the parents
name instad of the parent. Silly mistake, sorry for wasting your time.
Since I write the query in a different place I didn't know it was actually
the framework that executed it.
--
You received this message because you
On Oct 26, 2011, at 6:50 PM, Michael Bayer wrote:
>
> OK you're getting confused here
If I had a nickel =P
>
> So this is something occurring on usage, not on the mapping, which is not
> shown here.Somewhere a string value is being passed where an object
> should be, such as if you were
