On Thu, Jun 4, 2009 at 11:19 AM, Brian May
<br...@microcomaustralia.com.au> wrote:
>
> On Thu, Jun 04, 2009 at 10:27:35AM +0800, Russell Keith-Magee wrote:
>> If you're going to start throwing around claims that loaddata/dumpdata
>> doesn't work, you _really_ need to back them up with a demonstrated
>> example that proves your claim. We provide Trac for precisely this
>> reason, and you will find that claims of data corruption are taken
>> very seriously by the core developers.
>
> Like I said this was a while ago, I think a test case that shows curruption
> with Django 0.96 would be pointless.

It isn't pointless in the least. The problem _might_ still exist - we
have no way of knowing, because this is the first time you've reported
it, so we've never made an explicit attempt to fix it. As it currently
stands, you have no way of knowing if your problem has been fixed
(inadvertently or directly).

> I don't expect anybody to take my claims too seriously,

You are correct that a single comment probably doesn't matter that
much. However, it matters a great deal in aggregate. You probably
won't be quoted directly, but one person saying "I've had data
corruption problems" becomes a few people saying "I've heard Django
has data corruption problems", which becomes "Everyone knows Django
has data corruption problems" - eventually the meme gains traction,
even if it is completely untrue. Case in point - the "Rails doesn't
scale" meme from a few years ago.

> the problems I
> encountered were probably fixed ages ago. I don't like to assume something is
> fixed though unless I have some confirmation.

Instead of hoping that your problem was "probably fixed ages ago", how
about helping us confirm that it _has_ been fixed, or if it hasn't
been fixed, then helping us fix it. A test case is the first step.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to