Re: change of m2m field not reflected

pretty sure that's the solution to my problem. Again, thanks a lot. Best regards, Georg Göttlich --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to dj

change of m2m field not reflected

in advance. Beste regards, Georg Göttlich --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group,

Re: annotate() type coercion

Hello Karen, thanx a lot for the information and sorry for being so unspecific. Sounds like my problem. I'm using python 2.5 and sqlite3 (in my dev environment). So I'll try to upgrade sqlite. Cheers, Georg On 26 Aug., 14:05, Karen Tracey <kmtra...@gmail.com> wrote: > 2009/8/26 Georg

annotate() type coercion

Hello everybody, I'm not sure if this is a bug in django or if it works as designed. That's why I'm asking here first, before filing a bug. When using annote() on a model, it's date values become unicode values. Is this normal behavior and if so, is there a way to prevent this? Cheers, Georg

Re: Raw SQL and model instances

Hello Russ, thank you very much. This is exactly what I wanted to know. Best regards, Georg Göttlich --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email

Raw SQL and model instances

Hello everybody, this question has probably been ask quite often already, but I couldn't find anything proper on it. So here it is: Is there a way to feed the result cursor of a custom sql query back into the ORM, thus recieving model instances, as if you'd use a queryset? Thanks a lot, Georg