OK thanks very much for the reply Malcolm. On Apr 21, 3:47 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Fri, 2007-04-20 at 20:00 +0000, Jamie Pittock wrote: > > Hi all, > > > I'm currently planning my first Django application and after a quick > > search of groups I need a model structure very similar to that mention > > in this thread: > > >http://groups.google.com/group/django-users/browse_thread/thread/4835... > > > Basically I need models for Restaurant, Bar, Hotel etc but it would be > > useful to have a parent model Place that could contain the fields > > general to all the models, plus it would be useful so that a > > restuarant and bar wouldn't have the same ID, or at least they'd have > > a unique Place ID. > > > Has Model Inheritance moved on at all since that previous thread? > > Not yet. > > > Is > > a OnetoOneField the best option, > > Yes. > > > or ,given that (after another quick > > search) it seems Model Inheritance may well be back in the not too > > distant future, > > Correct. > > > is there another option that would make an easy > > transition once it is supported? > > Use one-to-one now and change it to MI later. The changes won't be that > significant. A few quick search-and-replace operations in your templates > and views should do it. > > Cheers, > Malcolm
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
