Hi,
DatabseFeatures class has a supports_transactions property for test if the
db engine support transactions.
supports_transactions implementation makes some metadata alters to check
this behaivor.
Now, is really needed to do this to check transaction support?
I don't know exactly how many t
The gremlin example was just a light-hearted attempt at justifying the
claim of "data corruption", in response to Florian, but I really only
brought up this issue because it surprised me (nothing in the docs).
I would suggest a docs update to let developers know that if a default
isn't set, ``F
On Tue, Sep 25, 2012 at 8:00 AM, Yo-Yo Ma wrote:
> Developer of a pet shop software adds:
>
> feed_before_midnight = models.BooleanField()
>
> because they're planning on carrying baby gremlins... forgets to update the
> zoological XML feed importer to use the "feed_before_midnight" value, and
> t
On Sunday 23 September 2012 15:05:21 Anssi Kääriäinen wrote:
>
> If you decide to work on this, please split the patch into two: one
> for the ._rowfactory change, one for the feature addition. My belief
> is that the ._rowfactory change is going to be something we can very
> easily justify commi
Developer of a pet shop software adds:
feed_before_midnight = models.BooleanField()
because they're planning on carrying baby gremlins... forgets to update the
zoological XML feed importer to use the "feed_before_midnight" value, and
the rest is history :)
On Monday, September 24, 2012 9:21:34
Hi everyone,
This may be interesting to some of you. I created a small library for
inheritance of *a set of* models.
It's best to go quickly through the Readme on the site below.
We felt a need for this, but I'm wondering whether some kind of inheritance
like this has been discussed before. And
2012/9/24 Florian Apolloner
> I don't see how that could corrupt stuff in the current situation, I'd
> rather argue that fixing the bug will cause more issues since people
> probably (I am sure I do) do unknowingly rely on the current behavior. As
> such we will exercise caution here and won't co
On Monday, September 24, 2012 3:07:37 PM UTC+2, Yo-Yo Ma wrote:
>
> Yep, that looks like it. IMHO, this is a bug that should be fixed without
> delay, as it breaks a cardinal rule for Pythonistas, and could even lead to
> a "data corruption" situation, if a dev was to add a boolean field and
> f
Yep, that looks like it. IMHO, this is a bug that should be fixed without
delay, as it breaks a cardinal rule for Pythonistas, and could even lead to
a "data corruption" situation, if a dev was to add a boolean field and
forget to update a form or fixture, or both.
On Monday, September 24, 201
Hi folks --
A reminder: we're going into feature freeze for the 1.5 release on
October 1st*, one week from today. This means that any features you
want to get into 1.5 need to land this week.
Practically, this means that if you don't have a patch/pull request
open for review in the next day or tw
2012/9/24 Yo-Yo Ma
> This may be the intended behavior, but I couldn't find docs on it. My
> recommendation would defer to "The Zen of Python"
>
> In the face of ambiguity, refuse the temptation to guess.
>
> I would rather see the typical IntegrityError: Problem installing
> fixture...
Hel
11 matches
Mail list logo
