On Sat, Jun 2, 2012 at 5:39 AM, Ian Kelly <[email protected]> wrote: > On Fri, Jun 1, 2012 at 12:29 PM, Vinay Sajip <[email protected]> wrote: >> >> On Jun 1, 6:39 pm, Ian Kelly <[email protected]> wrote: >>> >>> The error is caused by one of the column names in the table. See the >>> second paragraph at: >>> >>> https://docs.djangoproject.com/en/1.4/ref/databases/#naming-issues >>> >> >> Thanks, that helped. It seems that in this case, the offending name is >> 'date'. I added a db_column='event_date' and all seems well. As this >> is a standard Django regression test, I presume a ticket should be >> raised? > > I don't think a whole ticket should be needed for this, just a pull > request. It's the kind of thing that I would have just committed > without a ticket back when we were using subversion. I'm a bit out of > touch with process these days, though, so I could be wrong.
For auditing purposes, a ticket is always helpful, even if the ticket is closed straight away. That way, anyone who hits the same problem later on can see the source of the problem and the fact that a solution should be coming in the near future. It would also be nice to be able to catch these problems as an automated validation process… but that's a much bigger issue. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
