Adam M Peacock wrote:
Is there a difference in the SQL executed when using lazy vs eager
loading? Specifically, if I use eager loading will everything be
queried at once with a more efficient join, or will it still use the
lazy style (as far as I understand it) of generating a ton
FYI, polymorphic associations to concrete mappings are totally
unsupported in Hibernate, an ORM that has a lot more maturity,
widespread usage, and developers on it than this one...leaving me
fairly uninspired to worry much about SA's similar limitations with
polymorphic concrete mappings
On Feb 22, 6:04 am, Manlio Perillo [EMAIL PROTECTED] wrote:
Michael Bayer ha scritto:
its what it says...its updating the database and not finding the rows
it expects, indicating some other concurrent process already deleted
that row.
Is this actually possible, even if each query run
Are there any plans to handle circular dependencies by using
deferrable foreign key constraints when available?
In my case, I had made the foreign key constraints deferred, but
SQLAlchemy didn't pick up on that when I reflected the database
metadata. I eliminated the circular dependency by using
try putting primaryjoin=... inside the backref()
I've been trying to recreate the self referential 'parent/child'
mapper tutorial:
http://www.sqlalchemy.org/docs/adv_datamapping.myt#advdatamapping_s
elfreferential
I keep getting the following error:
Error determining primary and/or
ive heard of foreign key constraints that dont take effect until the
tranasction actually commits, but I have never actually seen this in
practice. which databases support this feature ? i didnt think it
was so common (though not surprised PG supports it).
On Feb 22, 2007, at 1:15 PM,
