Ok,
I get it working. See below.
On Dec 7, 2007 4:09 PM, Bert Wesarg [EMAIL PROTECTED] wrote:
Hello all,
I need a little help, guidance to get a Many-to-Many Adjacency
Relationships, a.k.a. a dependency graph working.
Here is the short code:
metadata = MetaData('sqlite:///')
hmm strange, i tried this out with sqlalchemy version 0.4.1 but it
does not seem to work...
s.name
u'HALN01100601'
isinstance(s.name, sqlalchemy.orm.PropertyLoader)
False
s.targets
[tcd_sample_database.model.samples.Target object at 0xb608dcac]
isinstance(s.targets,
Hi.
I suggest that the attached patch be applied to trunk. I was working
on a small database-comparison tool which used != between two
RowProxy objects, and it took me a little while to realize that it was
not behaving equivalently to == negated.
--
Knut Aksel Røysland
On Dec 8, 2007, at 2:09 PM, Brendan Arnold wrote:
hmm strange, i tried this out with sqlalchemy version 0.4.1 but it
does not seem to work...
s.name
u'HALN01100601'
isinstance(s.name, sqlalchemy.orm.PropertyLoader)
False
s.targets
[tcd_sample_database.model.samples.Target object at
I am very pleased to announce that version 0.5.0 of Elixir
(http://elixir.ematia.de)
is now available. As always, feedback is very welcome, preferably on Elixir
mailing list.
This is mostly a bug fixes release, but we have also had some pretty
important changes to the default values for options.
t1, t2 =
Table1.options(undefer(table2.large_col)).join(table2).add_entity(Table2).first()
does not load large_col (or even put it in the SQL sent) on t2. Is
undefer meant for eager loading in this scenario only, or have I
stumbled upon a bug? (if the former, is there a way to achieve what I
was
On Dec 8, 2007, at 6:17 PM, Chris M wrote:
t1, t2 =
Table1
.options
(undefer
(table2.large_col)).join(table2).add_entity(Table2).first()
does not load large_col (or even put it in the SQL sent) on t2. Is
undefer meant for eager loading in this scenario only, or have I
stumbled upon a
options() could work like joinpoints do - after an add_entity,
options() refers to that entity.
On Dec 8, 7:12 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Dec 8, 2007, at 6:17 PM, Chris M wrote:
t1, t2 =
Table1
.options
(undefer
On Dec 8, 2007, at 7:25 PM, Chris M wrote:
options() could work like joinpoints do - after an add_entity,
options() refers to that entity.
probably. ive been hesitant to make things go off of add_entity() as
of yet.though actually this is probably not very hard to do. youd
have to
One thing I'd be worried about is that after an add_entity there is no
way to set options on the main entity afterwards. You could provide a
reset_entitypoint, but it wouldn't work the same as with joins because
after a reset_joinpoint you can rejoin along the same path to filter
more criterion
On Dec 8, 2007, at 9:55 PM, Chris M wrote:
One thing I'd be worried about is that after an add_entity there is no
way to set options on the main entity afterwards. You could provide a
reset_entitypoint, but it wouldn't work the same as with joins because
after a reset_joinpoint you can
11 matches
Mail list logo
