[sqlalchemy] Re: Mapped class and c attribute in 0.5

2008-07-09 Thread Luis Bruno
Michael Bayer escreveu: in 0.5, the attributes on classes vs. the columns on Tables are very different beasts now. Got bitten by this too; I'm using MappedClass.c.keys() to serialize all attributes of a class but don't want to write out every field name. Should I use

[sqlalchemy] Re: Mapped class and c attribute in 0.5

2008-07-09 Thread Michael Bayer
On Jul 9, 2008, at 12:10 PM, Luis Bruno wrote: Michael Bayer escreveu: in 0.5, the attributes on classes vs. the columns on Tables are very different beasts now. Got bitten by this too; I'm using MappedClass.c.keys() to serialize all attributes of a class but don't want to write out

[sqlalchemy] Re: Mapped class and c attribute in 0.5

2008-07-09 Thread Luis Bruno
Michael Bayer escreveu: Luis Bruno wrote: items = dict() for field in self._sa_class_manager.keys(): items[field] = getattr(self, field) Is there a simpler way, perhaps? obj.__dict__ is available as always for reading, I'd think thats the easiest way to get at current object

[sqlalchemy] Re: Mapped class and c attribute in 0.5

2008-06-25 Thread Michael Bayer
On Jun 25, 2008, at 10:48 AM, Huy Do wrote: Hi, I read in the 0.5 release notes that the c attribute was no longer necessary when doing queries using the mapped class, but I did not see it mentioned that the c attribute was removed all together. It's just that I've been using the c

[sqlalchemy] Re: Mapped class and c attribute in 0.5

2008-06-25 Thread Huy Do
Michael Bayer wrote: On Jun 25, 2008, at 10:48 AM, Huy Do wrote: Hi, I read in the 0.5 release notes that the c attribute was no longer necessary when doing queries using the mapped class, but I did not see it mentioned that the c attribute was removed all together. It's just that