Calling any Oracle developer (Matt Boersma?, Ian Kelly?),
I see that the Oracle backend has had savepoint support since [10022]
in March.
I'd like to understand whether this was done:
a) simply to add the feature (which is good!)
b) "by necessity" to be able to perform savepoint rollback when a
My question is effectively the same as asking if the test suite passed
on Oracle between [8314] in August 2008 and [10022] in March 2009.
I assume that it must have passed during those six months (Django 1.0
was [8961] in September 2008!), which would imply that Oracle
savepoints were implemented
On Sat, May 16, 2009 at 1:42 PM, Richard Davies
wrote:
>
> My question is effectively the same as asking if the test suite passed
> on Oracle between [8314] in August 2008 and [10022] in March 2009.
>
> I assume that it must have passed during those six months (Django 1.0
> was [8961] in Septembe
Hi all,
I officially began work this week (for some value of officially that doesn't
include the official GSOC project starting :) ). I've had good success in
getting a lot of the ground work laid, specifically I got the connections
object in, updated a bunch of management commands for a --databa
Hello!
We must not try to select Site object from DB in
django.contrib.contenttypes.views.shortcut if no Site model is
installed.
Can somebody pay some attention to this ticket, review and may be
commit one-liner patch? =)
http://code.djangoproject.com/ticket/11129
Thank you!
--
Best regards,
S
On Sat, May 16, 2009 at 6:18 PM, Sergey Belov wrote:
>
> Hello!
>
> We must not try to select Site object from DB in
> django.contrib.contenttypes.views.shortcut if no Site model is
> installed.
> Can somebody pay some attention to this ticket, review and may be
> commit one-liner patch? =)
> htt
Just want to step out of lurker mode and pipe up with my modest +1.
I've been able to hack together simple denorm tricks for FK fields and
static data that work something like these fields -- but one thing I could
really use some help with yet is pulling off denormalization of frequently
changing