[BioPython] [bip] [OT] Revision control and databases

[Leighton Pritchard]

Hi Giovanni,

On 23/10/2008 12:30, "Giovanni Marco Dall'Olio" <dalloliogm at gmail.com>
wrote:

> The problem is I don't know if databases do Revision Control.
> When I used flat files, I was used to save all the results in a git
> repository, and, everytime something was changed or calculated again, I did
> commit it.
> Do you know how to do this with databases? Does MySQL provide support for
> revision control?

Databases are just collections of data.  Database Management Systems (DBMS)
such as MySQL and PostgreSQL do not (AFAIAA) do revision control themselves,
but they can be used for it, if you build that capability into the schema
and also control database submissions appropriately.  There are a number of
content management systems that implement version/revision control on common
DBMS, like this.

Stretching a definition, you could possibly argue that CVS, SVN and the like
are a form of DBMS... I don't know what type of data you're storing, or how
they might scale for your purposes but, in principle, neither CVS nor SVN
care much about whether your data represents code, legal documents, or any
other sort of data.  For example, I've used CVS/SVN to version control
manuscripts.  You might like to try one of them.

Cheers,

L.

-- 
Dr Leighton Pritchard MRSC
D131, Plant Pathology Programme, SCRI
Errol Road, Invergowrie, Perth and Kinross, Scotland, DD2 5DA
e:lpritc at scri.ac.uk       w:http://www.scri.ac.uk/staff/leightonpritchard
gpg/pgp: 0xFEFC205C       tel:+44(0)1382 562731 x2405


______________________________________________________________________
SCRI, Invergowrie, Dundee, DD2 5DA.  
The Scottish Crop Research Institute is a charitable company limited by
guarantee. 
Registered in Scotland No: SC 29367.
Recognised by the Inland Revenue as a Scottish Charity No: SC 006662.


DISCLAIMER:

This email is from the Scottish Crop Research Institute, but the views 
expressed by the sender are not necessarily the views of SCRI and its 
subsidiaries.  This email and any files transmitted with it are
confidential

to the intended recipient at the e-mail address to which it has been 
addressed.  It may not be disclosed or used by any other than that
addressee.
If you are not the intended recipient you are requested to preserve this

confidentiality and you must not use, disclose, copy, print or rely on
this 
e-mail in any way. Please notify postmaster at scri.ac.uk quoting the 
name of the sender and delete the email from your system.

Although SCRI has taken reasonable precautions to ensure no viruses are 
present in this email, neither the Institute nor the sender accepts any 
responsibility for any viruses, and it is your responsibility to scan
the email and the attachments (if any).
______________________________________________________________________