On Wed, 13 Jun 2007, Matt S Trout wrote:
On Wed, Jun 13, 2007 at 01:24:10PM +1000, Brad Bowman wrote:
A. Pagaltzis wrote:
* Daniel McBrearty <[EMAIL PROTECTED]> [2007-06-12 23:35]:
this is pretty much only for use in very limited circumstances.
Depends. The app I am mainly working on is a system for versioned
ad-hoc-structured compound documents. A scheme like that (only
much fancier) is the only reasonable approach.
What Iÿÿm building is quite unusual, though.
Shiny. At least one project I'm working on is likely to need some kind
of versioning and I'd like to know more about your approach.
(I envision using meta-data text files and source code version control tools
in my situation but probably could still learn from your work)
As soon as 08 goes out then trunk/DBIx-Class-Audit will ship.
That'll enable you to keep full version history for any/all tables within
your schema, which is what I'd use in that case.
You neant trunk/DBIx-Class-Journal ;)
Testers welcome!
Jess
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/[email protected]/
