Tuesday, January 31, 2012

Dynamic runtime modeling: which is the best choice?

Hi list.
I need to create an app in which the user can upload a shapefile, which
must be stored in a database table with LayerMapping from
django.contrib.gis.utils, as explained here:
https://docs.djangoproject.com/en/dev/ref/contrib/gis/tutorial/#layermapping

The problem is that I need to update dynamically my models.py with a new
model and add a table for every shape inserted by the user, without
using syncdb.

Trying to document myself about this topic, I encountered a lot of
interesting extensions like south, django-eav and django-mutant for example.
(An interesting discussion here:
http://stackoverflow.com/questions/7933596/django-dynamic-model-fields/7934577#7934577)

But I'm very confused about what could be the best solution for my needs.

Has anybody experience with this kind of tools?

Thanks in advance.

Alessandro

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment