Jon Nelson wrote:
I encountered an odd issue today that I can't explain, and it seems like a
bug.
I've checked 0.5.4p2 and 0.5.5, and the behavior is the same.
its a mistake I've seen before. Backrefs change the collection, so the
iteration ends up granting only every other item.
#
Hello,
It took me a couple of days to narrow this down. It appears that when
object inherits from another object via joined table inheritance (I
haven't tested the other two inheritance modes), mapped attributes
defined as SQL expressions don't load correctly.
In the example below I have a
ticket 1480 is added for this issue which includes a patch to repair the
immediate test case. It does not yet cover the case where the column
expression takes the parent table into account.
bojanb wrote:
Hello,
It took me a couple of days to narrow this down. It appears that when
object
On Tue, Jul 21, 2009 at 1:10 PM, Jon Nelsonjnel...@jamponi.net wrote:
On Tue, Jul 21, 2009 at 10:47 AM, Michael Bayermike...@zzzcomputing.com
wrote:
Jon Nelson wrote:
I encountered an odd issue today that I can't explain, and it seems like a
bug.
I've checked 0.5.4p2 and 0.5.5, and the
Jon Nelson wrote:
The parent_id is NOT NULL and has no default. Doing something like
this doesn't seem to help, with or without the post_update=True (or
False) configured on the mapper.
the NOT NULL makes it impossible, unless you execute a sequence yourself
and populate both columns before
Can anyone explain what exactly this error refers to?
Thanks
VJ
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from
Vic wrote:
Can anyone explain what exactly this error refers to?
that error should be impossible to create with 0.5.4 and above at least
(probably with previous versions as well). it is a class-level variable
that is referenced within a single module only and can only raise an
AttributeError
it is news to me that SQLAlchemy's table reflection code would even read a
SQLite view (and that sqlite had views, actually).Make sure your
view defines character based fields as VARCHAR, CHAR or similar.
note that SQLite has a very casual notion of types so you can make up any
type names
