I'm doing some experiments to see what is the best approach to write a
lot of data on disk,
On file and running commit after every opoeration: Function in_file
took 64.531976 seconds to run
In memory and not dumping to file: Function in_memory took 0.242011
seconds to run
On file and
Hi Michael,
I have a similar (but subtly different) problem to this, trying to mix
single- and joined-table inheritance.
Essentially my model looks as follows:
Product(Base)
PhysicalProduct(Product)
NonPhysicalProduct(Product)
The Physical/NonPhysicalProduct use single table inheritance
On Aug 22, 2012, at 11:38 PM, Warwick Prince wrote:
Thanks Michael
I struggle sometimes to find examples of the simple things, so eventually
searched out the like_op as it was in the same place as eq() etc.
So, on that subject - is it better to use query.where(eq(a, b)) or
Sorry to bring back a dead thread, but assume others like myself may
stumble here for help with this issue.
I added a hack to make sqlalchemy backwards with regards to the
transactional keyword and thought it may be useful for future releases.
While upgrading a project to avoid deprecated
On Thursday, August 23, 2012 3:01:50 AM UTC+1, Michael Bayer wrote:
On Aug 22, 2012, at 5:33 PM, David McKeone wrote:
I suppose I should be more clear. This is really a long term question,
I was just looking for some kind of answer now because I don't want to code
myself into a
OK - cool.
I had looked at the first ORM tutorial, but I guess I had glossed over it, as
it was talking about session.query, and I believed I was looking for something
lower level than that for the direct table.select. Obviously not. :-) Makes
sense that it would all follow suit, but I was
