We're using the Django trunk (r5988), but are about to dive into adding some PostGIS geometry columns to a few of our models. It appears that GeoDjango is its own branch--has anyone got advice about whether we can use it with a more recent checkout than it branched from?
The GeoDjango additions look quite easy to use, a plus for our organization that's just getting started with GIS. If the trunk and GeoDjango AREN'T currently compatible, would it be possible for us to add geometry columns AFTER a syncdb creates the "standard" model tables? Would the automatic admin still work in such a situation? Thanks in advance for any advice you've got. Django is becoming our tool of choice for data that needs to have an editing interface for internal use and be queryable from our other applications and website. Cheers! -- David Hancock | [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
