Re: Dynamic runtime modeling: which is the best choice?

>         This sounds more like a need for shapefile translators (codecs, if
> you will)... On input you'd convert the contents into a common database
> format; reverse the process on output.

What is a "common database format"? If a shape file has 5 fields and
another one 10 (and I dont' know the fields name!) how can I
generalize this situation before getting those files?

>         IOWs, my view is that you should be storing the "shape" and not the
> "file".

What do yuo mean? LayerMapping is not the right way?

--
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.