You should explain more about what you are trying to do, and where the difficulties are. Ticket #419 is about abstract base classes for table-based models. It sounds like you want a model class that has nothing to do with tables ever. If the latter is the case, then simply create a Python class and do whatever you want with it.
For example, you can write a view function that pulls data from wherever you want (an RSS feed, a file on disk, a random number generator), then formats it as HTML and returns it to the browser. There's no need for a database to be involved. --Ned. http://nedbatchelder.com Nathan Fiedler wrote: > This topic has come up once or twice before, but it doesn't seem like > a solution exists. Basically I'm looking for a recommended pattern for > creating Django models that have no association with a database (i.e. > "tableless"). > > Curiously, ticket #419 has to do with enabling tableless models, but > it was resolved as "duplicate", with no reference to any other ticket. > Has this really been resolved, and if so, what happened? > > Thanks > > n > > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
