On Mon, Oct 19, 2009 at 5:03 PM, John Handelaar <j...@userfrenzy.com> wrote:
> > Hello > > For reasons I won't bore you with, a Mysql legacy DB *whose schema I > cannot alter* contains (inter alia) two tables. I'm trying to write > an alternative front-end to this DB in Django which would be > read-only. > > tableone has a primary key called tableone_id > > tabletwo contains rows which have a 1:1 relationship with equivalent > rows in tableone, and a column called tableone_id to allow me connect > them with a JOIN. It does not, however, have a primary key of its > own. > > It seems obvious to me that these two tables belong in one Model > definition. How do I define a single model which spans the two tables > and returns querysets containing all columns from both tables? > > This sounds like a multi-table model inheritance: http://docs.djangoproject.com/en/dev/topics/db/models/#id7 Models defined something like this: class TableOne(models.Model): tableone_id = models.AutoField(primary_key=True) ...whatever other fields are in this table... class TableTwo(TableOne): tabletwo = models.OneToOneField(TableOne, parent_link=True) .... whatever other fields are in this table... would seem to do what you want. If you need to ensure that the Django code never writes to these tables, just specify a database user in settings.py that has only SELECT permission for the tables, no UPDATE or INSERT. (And then don't write any Django code that would trigger updates or inserts.) 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 -~----------~----~----~----~------~----~------~--~---
