[Koha-patches] [PATCH] [followup](MT3160) fix address request

[Chris Cormack]

* Nahuel ANGELINETTI (nahuel.angelinetti at biblibre.com) wrote:
> Le 01/07/2010 10:00, Chris Cormack a écrit :
> >* Nahuel ANGELINETTI (nahuel.angelinetti at biblibre.com) wrote:
> >>Le 01/07/2010 02:03, Owen Leonard a écrit :
> >>>On Wed, Jun 30, 2010 at 11:03 AM, Michael Hafen
> >>><mdhafen at tech.washk12.org>   wrote:
> >>>>I have found in Mysql that CONCAT_WS handles NULL values well.  Have you
> >>>>looked into that?  The syntax is a little different from CONCAT.
> >>>Aren't we trying to avoid functions which are MySQL-specific?
> >>>
> >>Why ? Koha doesn't work with another DBMS...
> >>No one is maintaining the postgre structure, and I think all code is
> >>MySQL specific.
> >>My point of view, is the development of koha must do some good code
> >>for one DBMS, instead of bad code for all DBMS.
> >>For the moment, koha doesn't use an ORM that permit to use some
> >>DBMS, and don't take care about "SQL".
> >A major goal, for 3.4 as I have stated is for it to remove the mysql
> >specific sql. So while its galens call on this patch for 3.2. I wont be
> >accepting mysql specific sql for 3.4
> Why don't use an ORM to avoid ANY sql code ? And don't take care of
> writing SQL, just using functions like in Django :)

That may be a future plan, but for 3.4 being a short release cycle that
is well out of reach. I have already got a DBIx::Class Schema, and have
deployed that to postgres to get Koha running on it. Finishing combined
with all the other work set aside for 3.4 is more than a enough.

Chris
> 
> -- 
> Nahuel ANGELINETTI
> 
> _______________________________________________
> Koha-patches mailing list
> Koha-patches at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-patches

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand