Oracle savepoints

[Richard Davies]

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
transaction gets broken by IntegrityErrors

Savepoints were first implemented in Postgresql with [8314] last
August, and were implemented for reason (b). Once a Postgresql
transaction experiences an IntegrityError, it refuses all further
commands with "current transaction is aborted, queries ignored until
end of transaction block" until it has been rolled back to a prior
savepoint (see 
http://groups.google.com/group/django-developers/browse_thread/thread/c87cf2d97478c068/
, 
http://docs.djangoproject.com/en/dev/topics/db/transactions/#handling-exceptions-within-postgresql-transactions)

Are savepoints needed for this reason (b) in Oracle too, or are they
simply there as a feature for users?

i.e. does an Oracle transaction continue to function without savepoint
rollback after an IntegrityError?

Thanks,

Richard.
--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Oracle savepoints

[Richard Davies]

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 for reason (a) to add the feature rather
than reason (b) by necessity.

But please can someone confirm?

Thanks,

Richard.
--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Oracle savepoints

[Matt Boersma]

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 September 2008!), which would imply that Oracle
> savepoints were implemented for reason (a) to add the feature rather
> than reason (b) by necessity.

I think Malcolm implemented this in the Oracle backend rather than Ian
K. or myself.  The test suite has been passing all but a few cases on
Oracle in general since before the 1.0 release.

So I'd say the answer is a).

--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

[GSOC] Multi-DB Status Update - Week 0

[Alex Gaynor]

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 --database flag, and
started removing various uses of the global connection object.  I also got
the test harness more or less working with multi-db, however fixture loading
still only works with the primary DB, so any tests that rely on these will
fail if you have more than one database defined.

Therefore next week I think my first step is going to be to add support to
saving to a specific DB, because this will let me fix fixture loading, which
lets me run the full test suite, which is a good thing (TM).

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Site object in django.contrib.contenttypes.views.shortcut

[Sergey Belov]

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,
Sergey Belov

--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Site object in django.contrib.contenttypes.views.shortcut

[Alex Gaynor]

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? =)
> http://code.djangoproject.com/ticket/11129
>
> Thank you!
>
> --
> Best regards,
> Sergey Belov
>
> >
>
This is a duplicate of another ticket, and I have marked it as such.  That
ticket was marked for 1.2, as it isn't critical for the 1.1 release, as such
it will be reviewed in due time.

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Denormalisation Magic, Round Two

[Ben Welsh]

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 M2M fields. Do y'all think that's something that will have to wait
for M2m signals like ticket 5390
or can modifications to the
methods here make it work in 1.0? I haven't been
able to square the circle in my feeble brain, so here I am.

Love what you're doing,

Ben.



On Sun, Nov 30, 2008 at 3:33 PM, Christian Schilling <
initcr...@googlemail.com> wrote:

>
> On Nov 30, 9:55 pm, Andrew Godwin  wrote:
> > I have a Trac setup around on my server for South, so if you want I'll
> > kick that slightly and install the Git plugin...
>
> this should be  easier than setting it up on my server where i run
> debian/stable which contains only an old version of trac and no trac-
> git at all.
> >
>

--~--~-~--~~~---~--~~
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 from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---