Hi Michael,
declarative places a convenience __init__ that installs keywords as
attributes, but you're free to override this constructor with anything
you'd like.
Thank you for confirming this for me, I'd hoped I'd be able to override the
class constructor, I often use it for
i'm sorry for my misleading reply;(
i was kind of too sleepy last night;P
On Jul 13, 5:29 pm, Heston James - Cold Beans
[EMAIL PROTECTED] wrote:
Hi Michael,
declarative places a convenience __init__ that installs keywords as
attributes, but you're free to override this constructor with
i'm sorry for my misleading reply;(
i was kind of too sleepy last night;P
No problem my man.
Heston.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
It fails with fields of date. It shows:
created_at=*datetime.datetime(2008, 7, 13, 13, 59, 57)*
On Jun 21, 7:25 pm, Michael Bayer [EMAIL PROTECTED] wrote:
that __repr__ is pretty tortured too; a typical ORM-agnostic approach
is:
def __repr__(self):
return %s(%s) % (
Hi,
I'm not sure if this is really a bug but at least it's not intuitive... :)
I'm trying to determine if the primary key for a table will be
autogenerated by the database or not by peeking into
Column.autoincrement, however, the following unit test fails:
import unittest
from sqlalchemy import
On Sunday 13 July 2008 08:14:47 Kyle Schaffrick wrote:
On Sat, 12 Jul 2008 22:01:50 +0300
[EMAIL PROTECTED] wrote:
after the Query is long gone?
if it is really gone/done, who should eager-load?
I assume that it would be possible to do it after the Query is
gone, at least in theory,
On Sunday 13 July 2008 21:46:24 Kyle Schaffrick wrote:
On Sun, 13 Jul 2008 19:02:03 +0300
[EMAIL PROTECTED] wrote:
I assume that it would be possible to do it after the Query is
gone, at least in theory, since lazy-loaded attributes are able
to trigger eager-loads on attributes of
i'm trying to understand what exactly u want...
do u want (for an a.b.c.d chain) to query on a (with b being
lazy), then _later_ tell b.c.d to be eagerloaded and then
lazyload b? i.e. some sort of options-of-relation-loading like
those of-query-loading? taking a relation closer to a
if u want i can give u example tomorrow on the turning the tables. i
did such thing yesterday on my bitemporal query-lib, turning a loop
inside out like a coat, plus adding extra entry point.
but it might be dense to digest, my style is to not write anything
twice if it can be said once (eh
Hello
I created my own type, Geometry, to deal with PostGIS' geometry column type.
class Geometry(TypeEngine):
def __init__(self, srid=-1, dims=2):
super(Geometry, self).__init__()
self.srid = srid
self.dims = dims
def get_col_spec(self):
return
On Jul 13, 2008, at 5:29 AM, Heston James - Cold Beans wrote:
Hi Michael,
declarative places a convenience __init__ that installs keywords as
attributes, but you're free to override this constructor with
anything
you'd like.
Thank you for confirming this for me, I'd hoped I'd be able
On Jul 13, 2008, at 9:49 AM, Alberto Valverde wrote:
Hi,
I'm not sure if this is really a bug but at least it's not
intuitive... :)
I'm trying to determine if the primary key for a table will be
autogenerated by the database or not by peeking into
Column.autoincrement, however, the
On Jul 13, 2008, at 1:38 PM, Kless wrote:
*orm.object_mapper* has an argument called 'raiseerror', and it works
ok.
*orm.object_mapper.get_property* also has an argument called
'raiseerror' (that says on documentation), but it fails: *unexpected
keyword argument 'raiseerror'*. It's using
On Jul 13, 2008, at 1:47 PM, [EMAIL PROTECTED] wrote:
hi all
i have a tree/graph of nodes and links inbetween (= explicit m2m), and
many users can simultaneusly change nodes/links.
i need to get all-reachable-from-x in one query - so i'm saving also
all the paths (not just the immediate
14 matches
Mail list logo
