Re: get_or_create can still cause IntegrityError

2011-05-07 Thread David Cramer
Would it help (in PG-world) at least if the selects where in savepoints as well? On May 7, 10:09 am, David Cramer wrote: > We hit this same issue in Postgres (it's definitely not MySQL > specific). I'm unsure of the solution or precise conditions we're > hitting it in, but I think by default we u

Re: django.conf.settings.get()

2011-05-07 Thread Luke Plant
On 07/05/11 18:13, Alex Gaynor wrote: > I'm -1, it's literally a one line substitute for a Python builtin, it > adds zero value. I agree with Alex, and with James (ubernostrum) who closed it originally. Luke -- O'REILLY'S LAW OF THE KITCHEN Cleanliness is next to impossible. Luke Plant ||

Re: django.conf.settings.get()

2011-05-07 Thread Alex Gaynor
On Sat, May 7, 2011 at 1:06 PM, David Cramer wrote: > Ticket speaks for itself: > > http://code.djangoproject.com/ticket/10098 > > My vote is to reopen it, as this is very common, easy to implement, > and very unlikely that it would ever need deprecated. > > -- > You received this message because

Re: get_or_create can still cause IntegrityError

2011-05-07 Thread David Cramer
We hit this same issue in Postgres (it's definitely not MySQL specific). I'm unsure of the solution or precise conditions we're hitting it in, but I think by default we use READ COMMITTED. On May 7, 3:28 am, Tomasz Zielinski wrote: > I think that get_or_create is still broken, despite this > fix

django.conf.settings.get()

2011-05-07 Thread David Cramer
Ticket speaks for itself: http://code.djangoproject.com/ticket/10098 My vote is to reopen it, as this is very common, easy to implement, and very unlikely that it would ever need deprecated. -- You received this message because you are subscribed to the Google Groups "Django developers" group.

get_or_create can still cause IntegrityError

2011-05-07 Thread Tomasz Zielinski
I think that get_or_create is still broken, despite this fix: http://code.djangoproject.com/ticket/6641 The details, along with a working solution, are in my answer here: http://stackoverflow.com/questions/2235318/how-do-i-deal-with-this-race-condition-in-django/2235624#2235624 I'm not sure if t

Odp: Re: model fields options

2011-05-07 Thread Mateusz Harasymczuk
In my opinion Meta class may contain this kind of information, and it would simplify the process of designing models. Especially handling fields which contains a lots of data inserted via arguments. However, I think that the Meta class properties should be an alias or a handy shortcut, not one