On Wednesday, July 07, 2010 09:38:55 Paul Johnston wrote: > Hi, > > > You mean you want a declaration for one field that says "this field is > > the __unicode__"-representation? > > Yep > > > What is the behavior for several such columns having that attribute? > > Exception when defining the class
Which would make the point for defining it on the class. Then one avoids that error-case all together. > > > How is coercion/decoding handled, which btw your example > > lacks? > > Normally you'd use a unicode column and avoid this issue. If you use a > string column, then it does the default python conversion, just like > my example. Which might fail. What is your actual use-case btw? Is it really for converting to unicode, or more to have some declarative repr-functionality? That I'd like to see. Diez -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en.
