On Thursday 15 September 2005 23:44, Viktor Pracht wrote: > > SVN provides out of the box: > * remote access, > * atomic changes, > * complete history of all changes, which implies changes are immutable > yet easy to correct, while the correction itself gets logged too. > > What it does _not_ provide out of the box is the enforcement of allowed > changes. For this, I just found out, there already are hooks: > http://svnbook.red-bean.com/en/1.1/ch05s02.html#svn-ch-5-sect-2.1
It also doesn't provide live replication. If the box on which the SVN repository is hosted dies, the number log is gone. And what if the box crashes? Does SVN guarantee that any data written is not corrupted in that case? It seems that Postgres supports replication via Slony (http://www.slony.info) It also supports log exporting for offline backups (databases keep logs, just like journaling filesystems, to ensure that if the system crashes any partially complete transactions can be undone, and any committed transactions that weren't written to disc yet can be redone). Saving historical information is just a matter of organising the tables properly (i.e. allow multiple entries with the same part number, if they have a different date) and modifying the queries (get the latest version of each number rather than everything). However, this would still require more work right now than just using the SVN repository. Most importantly, we'd need an experienced Postgres DBA to set it up. While I know my theory, I don't have enough practical experience to do that and be certain it's done correctly. Lourens
pgpoXd6kj4lsh.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
