On Saturday 14 June 2008 06:50:23 Russell Warren wrote:
so far i have found these ways to hack somebeody else's source:
a) inherit the class, replace whatever, use the new version -
works if it is just you using the new-stuff
b) complete replacement: import thatclass; thatclass.method =
On Saturday 14 June 2008 06:28:58 Russell Warren wrote:
if you'd like to specify a value generator for the columns, just
use a ColumnDefault. Whatever function or SQL you like will be
called if no value is present - its just in this case we can't
rely upon SQLite's OID generation.
Michael Bayer wrote:
oh. how are you getting it to join from soup- (album join
vinyl) ? soup has a relation to album join vinyl and you're
using query.join() ? it should be creating an aliased subquery for
the right side of the join in that case. I thought 0.4 was able to
do
I realize I'm doing something hacky, but I'm wondering if this is the
expected behavior. The issue is that if I modify the modifier on a
UnaryExpression, even if I clone the Query ahead of time it modifies
other Query instances. See the following:
import datetime
from
the _clone() on query is a shallow copy, otherwise it would be a serious
performance hit for a query that takes several generative steps to build
up. So you'd have to assign query's _order_by to a copy of itself if you
want to modify it in place like that. you can probably use
Russell Warren wrote:
Why not? Is it really guessing when the table has been defined
precisely within SQLA? If you have a Column that has been defined to
be an Integer primary key that is supposed to autoincrement, and you
are using sqlite... how could you be wrong?
autoincrement is very
