On Tue, Jun 23, 2009 at 12:04 PM, Greg Corey <gregco...@gmail.com> wrote:
> Ok. I will work on opening a ticket based on your recommendation, though I > will not have your depth of analysis on the problem. Mind if I quote your > most recent explanation if needed? > Sure, but it's probably not necessary, though you could include a pointer to this thread in the Google group's archive for the group for reference purposes. For the ticket description all you need to do is describe the problem from the user's level. You've got an existing database with a table that has a column name with a % in it. Unless you double the % when you specify it in db_column for the associated Django model field, you cannot access data in this table via your Django model. Needing to double the % in this parameter is entirely non-obvious and (I'm assuming -- you might want to verify this) not documented, so it either should not be necessary or needs to be documented. (If in fact you find that the description of db_column somewhere says %s in column names need to be doubled, then never mind about a ticket...but I'd be surprised if that were the case.) Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
