> Thanks Allan... we have used CVS for the base system.. but for users provided
> functions,
> we think for having them persistent in the database..
I'm puzzled. CVS provides much better facilities for handling code, especially
with multiple
versions (visibility of diffs, who changed what and when etc) that I can't
think of a single
good reason to put it in a database. I can see the point of using a database as
an indexing
system for searching, filtering etc but storing code in a database, extracting
it and then trying
to execute it is just so much more difficult than fetching a version file and
importing
or running it directly. Plus you need to write a basic version control system
on top of
the database anyway.
I really think I must be missing something about your requirements?
Alan G
On Thu, Nov 13, 2008 at 7:18 PM, Alan Gauld <[EMAIL PROTECTED]> wrote:
"Jojo Mwebaze" <[EMAIL PROTECTED]> wrote
Because we have very many such cases, we can not incorporate such adhoc
changes in the system.. we are thinking of storing such classes in the
database and have classes run from the database. if anyone else feels they
need to use someone's algorithm, they can run it/or extract it from the
database and run on it on their data.
Sorry if I'm missing the point but this sounds like a traditional version
control system like CVS or SVN would do the job using the normal
python files.
Or is that too simple?
--
Alan Gauld
Author of the Learn to Program web site
http://www.freenetpages.co.uk/hp/alan.gauld
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
