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

[Kyle Hall]

I would have to agree the patch order probably won't be an issue, as
each patch will still be added in the chronological order that it was
committed ( assuming every always adds to the end of the file as usual
).

Kyle

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




On Thu, Jan 28, 2010 at 4:07 PM, Michael Hafen <mdhafen at tech.washk12.org> wrote:
> Update order.  I hadn't thought of that.  That could be a big deal.
>
> I'm already committed to writing it if it does get traction.  I have a
> couple database updates in my own branch that couldn't be in the the
> updatedatabase.pl obviously.  If this does get traction and we can
> figure out the patch order thing I'll want this a lot.
>
> The patch order may not be that big a deal.  There is an implicit patch
> order enforced by the patches location in the updatedatabase.pl file.
> That might be good enough.
>
> On Thu, 2010-01-28 at 18:29 +0100, Paul Poulain wrote:
>> Kyle Hall a écrit :
>> > The naming convention sounds very reasonable. Very java import styled.
>> > Very good idea.
>> >
>> > Now the big question is, can we get any traction for such a big
>> > change? Is there anyone else willing to comment on the possbility of
>> > this idea?
>> >
>> create a syspref (with TEXT, we have a lot of space).
>> Separate each patch applied with a comma :
>>
>> BibLibre-1,mhafenA,someoneElse,anotherone,BibLibre-2, ...
>>
>> need to check that a patch has been applied ? just =~ /BibLibre-1,/ if
>> not applied, apply it, and add BibLibre-1, at the end of applied
>> patches. The order doesn't matter.
>>
>> (well, in fact, the order may matter, and that may be the limit of this
>> idea...)
>>
>
>
> --
> Michael Hafen
> Systems Analyst and Programmer
> Washington County School District
> Utah, USA
>
> for Koha checkout
> http://development.washk12.org/gitweb/
> or
> git://development.washk12.org/koha
>
>
>