Re: Django ORM and multidimensional data
Hallöchen! thierry writes: > Have django developers planned the integration of new model fields > capable to store multidimensional data? [...] > > By implementing this kind of basic types, I think it could be a > way for the Django project to reach the scientific community where > Python and databases are more and more popular to store > experimental and analyses data. I'm a member of a team that implements a samples database in our institute using Django. It's about keeping track of all depositions, etching processes, and measurements of our semiconductor samples. As far as storing measurement data in the database: We don't do that. Raw data is better stored in their original files in my opinion. It's equivalent to the old blob discussion. Such things shouldn't be in the database backend, but just the *pointer* to it. The web server has access to the raw data through shared directories (aka Samba). This way, Django still can generate plots of the raw data when this is suitable. This reduces redundancy, and it is efficient. Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus Jabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.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-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Django ORM and multidimensional data
On Fri, May 7, 2010 at 7:06 PM, thierry wrote: > Hi all, > > Have django developers planned the integration of new model fields > capable to store multidimensional data ? It's possible right now. As an example, GeoDjango contains fields for composite, multidimensional data (spatial points and polygons, for example) [1]. It's also possible to define your own custom fields to represent any data type that your database can represent, including transforming the data type returned by the database backend into a native Python datatype [2]. [1] http://docs.djangoproject.com/en/dev/ref/contrib/gis/model-api/ [2] http://docs.djangoproject.com/en/dev/howto/custom-model-fields/ > By implementing this kind of basic types, I think it could be a way > for the Django project to reach the scientific community where Python > and databases are more and more popular to store experimental and > analyses data. What sort of "basic" types did you have in mind? Django implements the field types that are reliably available across across all database backends. If there's a specific field type that you think is missing, and is available in a consistent way across multiple database backends, feel free to suggest it -- or better yet, try your hand at an implementation. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Django ORM and multidimensional data
Hi all, Have django developers planned the integration of new model fields capable to store multidimensional data ? If it's not the case, how can I submit this implementation request ? By implementing this kind of basic types, I think it could be a way for the Django project to reach the scientific community where Python and databases are more and more popular to store experimental and analyses data. Thanks, Thierry. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
