On 25/05/11 13:55, Ian Walls wrote:
I think the problem with database revision numbers comes down to something fundamentally structural. Database revision numbers are linear, and are part of the Koha version number. But our development is non-linear; using Git, we work off Directed Acyclic Graphs.
From a development point of view it would be helpful if changes were reversible. It might be easier to do this if the changes were in a separate directory with an individual files for each change and a script that pulled the relevant ones in. It might make it easier to isolate if a stage failed rather than having them all embedded in a script. ( I'm thinking along the lines of Rails which I seem to recall handled database schema changes rather neatly).
There's no single solution out there but I think we could definitely do better if we put our minds to it Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com