On Thursday 19 January 2012, Jeremy Dunck wrote:
> There's a known problem w/ latest pg (2.4.2) and we decided not to
> backport the fix to 1.3.x because there's a workaround.
>
> https://code.djangoproject.com/ticket/16250
>
> All well and good, but someone coming to Django w/ postgres will have
There's a known problem w/ latest pg (2.4.2) and we decided not to
backport the fix to 1.3.x because there's a workaround.
https://code.djangoproject.com/ticket/16250
All well and good, but someone coming to Django w/ postgres will have
a bad first-run experience because the docs don't mention th
On Wed, Jan 18, 2012 at 11:07 AM, Shai Berger wrote:
> Do you see a reason why I should not post a ticket?
+1
--
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 unsu
Hi Django devs,
I have a small improvement to suggest for one-to-one fields: Make them cache
back-references on related objects. That is, assume
class A(model):
pass
class B(model):
a = OneToOneField(A)
a1 = A.objects.get(...) # assume a1 has a related B record
