i know what that is, its fixed in rev 2281.

On Jan 30, 2007, at 2:27 PM, Dennis wrote:

>
> I decided to set a group of columns to be deferred.
>
> I have a situation in my code where I set the properties of an object
> in a loop.  After deferring the column group, the new object created
> can no longer set properties dynamically if I set the primary key
> columns first.
>
> Example:
>
> m=MyObject()
> m.primary_key_col=1
> m.__setattr__(name,val)
>   File "build/bdist.linux-i686/egg/sqlalchemy/orm/attributes.py", line
> 42, in __set__
>   File "build/bdist.linux-i686/egg/sqlalchemy/orm/attributes.py", line
> 232, in set
>   File "build/bdist.linux-i686/egg/sqlalchemy/orm/attributes.py", line
> 205, in get
>   File "build/bdist.linux-i686/egg/sqlalchemy/orm/strategies.py", line
> 104, in lazyload
> TypeError: unsubscriptable object
>
> If I however wait until after the attributes are set to assign the
> primary key columns, things work.
>
> m=MyObject()
> m.__setattr__(name,val)
> m.primary_key_col=1
>
> Perhaps the lazyload code doesn't have another mechanism besides the
> primary key to know if the properties need loaded or not.  If it does,
> there might be a simple workaround to avoid the nuance above.
>
> Thanks All
> -Dennis
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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 this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to