Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

In Defense of Version Locking More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Database schema version (Score:2)

by ask (83)

I do the schema versioning in my projects too.

Example data files:
https://svn.develooper.com/combust/trunk/sql/combust.update [develooper.com]
https://svn.develooper.com/projects/ntppool/trunk/sql/ntppool.update [develooper.com]

Script to run updates:
https://svn.develooper.com/combust/trunk/bin/database_update [develooper.com]

It has a --sql parameter that'll output the SQL instead of running it. Helpful when the production databases are run by a DBA team who don't have anything to do with the servers the code is on.

- ask

--
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Single versioning (Score:2)

by schwern (1528)

> It's partly for these reasons that I've been suggesting for a long time that
> people always release distributions where the versions for every module match.

Yeah, I'm coming around to that conclusion, too. The possible benefit of knowing specifically which modules in a distribution changed using individual version numbers is outweighed by just knowing what goes with what.

Also it's a pain in the arse to remember to only increment what's changed in the release.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.