Frederic Demians
> 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: [...]
I think a different way of handling database updates is a good idea
b
Dev Community,
I've added my script which I believe solves Ed's problem to contribs.koha.org.
http://contribs.koha.org/extension_view.php?eid=19
Hopefully this will prove helpful. I can work on adding an overwrite feature
in the next version (currently unwanted attributes must be removed man
Ed,
I think I've got a script that'll do what you need. Do you have command-line
access to your installation?
-Ian Walls
From: koha-devel-boun...@lists.koha.org
[mailto:koha-devel-boun...@lists.koha.org] On Behalf Of Roche III, Edward
Sent: Friday, January 29, 2010 1:14 PM
To: koha-devel@li
I posted the below email on the regular Koha list with no response.
Maybe a developer know of a good way to import extended patron
attributes.
Thanks!
Ed
Edward J. Roche
Network Administrator
Solanco School District
717.786.2151 x2437
"At the End of the Day, Did You Play to Win or N
On Fri, 2010-01-29 at 05:46 +0100, LAURENT Henri-Damien wrote:
> Imagine we had a column activate in your table where an active update
> would HAVE to be done.
> We would be able to "check" that it has been done.
I think it could be easier than that. If your update is dependent on
another update
> > 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
> > 'co
Frederic Demians a écrit :
> Those kind of things can be tricky and messy.
Other idea : shouldn't we open a new position, named "database
consistency manager" or something like that ?
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08
__
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
