I've got a legacy application with a few tables that only have a single row, e.g., for configuration information. I can easily get the info with the following hack: pick a column to be a pretend primary key (so that django doesn't add the id field), and use Model.objects.get(foo__isnull=False) - since there is only one row, I know that will work.
The problem arises when trying to modify the contents of the column that I'm pretending is the primary key: django will obviously insert a new row. There's a straightforward solution: modify the database schema to include an id column. I'm just wondering if anyone can think of a trick that doesn't require modifying the database structure. Thanks, Bill --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
