[Koha-bugs] [Bug 7167] updatedatabase improvements

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167

--- Comment #96 from M. de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to comment #95)
> _get_queries allows us to find potential problems with queries to execute
> (coherency on syspref, table/column name, permission) and to return a
> friendly structure ( {queries => [], comments => [] } ).
> With your suggestion, how can we know (to display) the queries to execute
> (or which had been executed) and the comments ?

First, I do not want to oppose this code (at this stage in time). It is in
itself of course good to check for potential problems, etc. 

I am just wondering: Are we really helping the developers or would it become
more complex? Suppose that I create a sql file with some statements spanning
multiple lines. Would it work with your approach? Why should we build some kind
of mysql tool if we can run the file with mysql just as is done during install
for other things?

I discovered that in a perl file I needed to define routines for these queries
and comments, and I did not think that it was easier. With just a use Context,
a db handle and the "old style" sql statements things seemed easier..

-- 
You are receiving this mail because:
You are watching all bug changes.