pure sql fixtures for tests

Hi, This is a bit of a continuation from this email in the other django group: https://groups.google.com/forum/#!topic/django-users/rRkYNt-cQOg The gist of it is this. More complex apps probably deal with with stored procedures, and columns not under direct django control (which is the case

Re: The model option's verbose_name_raw is not really that 'raw'

I see, thanks Didn't know the existence of the lazy translation, so this is all a big false alarm. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe fro

The model option's verbose_name_raw is not really that 'raw'

Hi, I think I might have stumbled upon a small bug. According to its docs, the 'verbose_name_raw' property is supposed to return an untranslated version of the 'verbose_name' property. However, if LANGUAGE_CODE is set, then 'verbose_name' would already be translated, provided that the user wrot

Re: the new SELECT DISTINCT query in 1.3 rc1, and how to turn it off

I've created a ticket for this http://code.djangoproject.com/ticket/15559 Also, if someone else is stumbling on this problem, I went around it by providing a custom QuerySet class for my method, which has an overridden distinct method, that returns itself. -- You received this message because

the new SELECT DISTINCT query in 1.3 rc1, and how to turn it off

Hello, I'm testing my software with the new rc1 release of django 1.3, and I came onto a particularly nasty problem. I have a model which uses a Postgresql 'point' type, for which I've defined a field as: http://dpaste.com/472467/ I also have another model, which references this one with a fore