[Koha-devel] How about a different way of handling database updates

[Kyle Hall]

I think this idea has snowballed into something way more complex than
the original idea, which I still prefer.

> My opinion is that the current system is not that bad. The dependency
> graph is linear, date ordered by version number last digits. It just
> becomes crazy when updates are ported from one branch to the other, HEAD
> to maintenance for example. And there is (am I wrong?) to claim
> 'communitly' such a number:

The problem with the wiki page for db number claiming is it doesn't
seem to work, at least it hasn't worked for me in the past. It assumes
that the features will be committed in the order that the db numbers
are claimed, which I don't believe is true. In that case, if the wiki
page were enforced, then db versions would be committed out of order,
and the updater would not work correctly. I just don't believe the
wiki page is effective at all. After having a number of db version
numbers stepped on, I stopped using it.

Kyle

http://www.kylehall.info
Information Technology
Crawford County Federated Library System ( http://www.ccfls.org )




On Fri, Jan 29, 2010 at 2:24 AM, Frederic Demians <frederic at tamil.fr> wrote:
> Those kind of things can be tricky and messy. Something like a
> dependency graph would be required, which is all but easy to implement.
> It has something to do with how patches are applied with git: order
> matters. 'git log --graph --pretty-oneline' displays s a representation
> of this order. Git manages pretty well its infamous 'conflicts' when
> merging branches, applying patches. Not sure it's possible to do that
> properly with DB updates.
>
> My opinion is that the current system is not that bad. The dependency
> graph is linear, date ordered by version number last digits. It just
> becomes crazy when updates are ported from one branch to the other, HEAD
> to maintenance for example. And there is (am I wrong?) to claim
> 'communitly' such a number:
>
>    http://wiki.koha.org/doku.php?id=en:development:dbrevs:start
>
> It should be used systematically.
>
> Extracting updates code from updatabase.pl script and putting it into a
> directory containing files named by version number could be a
> simplification: easier for RM to rename those files if required, not
> sure. It remains kohastructure.sql...
>
> --
> Frédéric
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha.org
> http://lists.koha.org/mailman/listinfo/koha-devel