On 6/22/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Wed, 2006-06-21 at 13:35 -0700, Tyson Tate wrote: > What are the use cases for this sort of construction? >
Here's another use case: you want to add fields to your table that don't have a representation in the Django model. For example - see Adrian's reply to a recent question about adding PostGIS fields into a Django-managed database. His solution was to create your table, then modify the table in model-specific initialization SQL to have fields with the GIS datatypes. Longer term, it might be nice to be able to support GIS fields (or allow a plugin to Django that supports them), but in the interim, a model that contains only GIS fields but is still referenced by a Django model would need to be empty from the Django perspective. Yours, Russ %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
