Hello,
this is what _relational_ databases are built for. if you have two
tables, one for the description of the experiment (one record per
experiment), and another for the statistics (one record per data
sample, with a foreign key to the experiment record); then fetching
the description of the experiment, plus all the related data will be
much faster, simpler, more compact and all-around more efficient than
having one table per experiment.
it looks to me that the resulting code should be more compact but more
difficult to write and maybe too clever for me. I'm writing this code
for someone who is not completely sure of what he really wants (I mean
the data that should be stored in the table) and so the code should be
able to accept some change in the definition of the experiments without
breaking the old data.
databases aren't flat files, use them as designed and they'll perform very well.
I agree with that. My main worry is that I'm not so familiar with
databases and I hope I can estimate if the code will perform well in
real condition when I'll do some limited tests.
thanks for the information and I'll give it a try
sincerely
L.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/54AEEE0B.3020408%40lpn.cnrs.fr.
For more options, visit https://groups.google.com/d/optout.
