Re: [Koha-devel] full text search
Anthony W. Youngman a écrit:
Have you read the MySQL licence ...
I don't know whether you're that bothered (Koha being gpl and all that), but the MySQL licence specifically splits systems built on top of it into ones that *can* *use* MySQL as one back end among many, and others that *need* *MySQL*.
As I say, since Koha is gpl maybe you don't care, but maybe others might ...
And if you're going to do this, for $DEITY's sake make it an *optional* module, so that should people not want MySQL, they can just leave this module out and then they're still independent ...
In fact, i think that the "need" mySQL refers to licence constraint : if your licence disable the opportunity for the user to use something else, then mySQL must be buyed. For us, as it's gpl, the "must" is a technical constraint, which is not covered by the mySQL constraint. MANY softwares works only on mySQL (1 "replace", which is mySQL-only, and your software is mysql dependant. And almost everybody uses replace when developping on mySQL) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIBGB libre http://fr.koha.org)
As I say, since Koha is gpl maybe you don't care, but maybe others might ...
And if you're going to do this, for $DEITY's sake make it an *optional* module, so that should people not want MySQL, they can just leave this module out and then they're still independent ...
In fact, i think that the "need" mySQL refers to licence constraint : if your licence disable the opportunity for the user to use something else, then mySQL must be buyed. For us, as it's gpl, the "must" is a technical constraint, which is not covered by the mySQL constraint. MANY softwares works only on mySQL (1 "replace", which is mySQL-only, and your software is mysql dependant. And almost everybody uses replace when developping on mySQL)
Yep Paul has hit the nail on the head.
On Tuesday 10 December 2002 11:23, Chris Cormack wrote:
When you distribute a non-GPL application that only works with the MySQL software and ship it with the MySQL software. This type of solution is actually considered to be linking even if it's done over a network.
Since we neither ship Koha with MySQL, nor is Koha non-GPL. The license is not an issue. And Koha and MySQL being GPLd prevents it from ever becoming one.
The technical constraint is the actual issue, and im not against binding koha to specific db in principle. If the benefits gained are such to warrant the disadvantages.
I think there's still a chance to mantain koha indepedent from a database engine while using specific database engine optimizations: A new abstraction layer may be created in places where optimizations are used. This layer could be implemented as a class. Something like this: package Koha::Search ... sub new { ... } sub search { $dbeng = shift; $keywords = shift; if (lc($dbeng) eq 'mysql') { # Perform search with mysql optimizations } elsif (lc ($dbeng) eq 'postgresql') { # Perform search with postgresql optimizations } elsif ... # Perform search with X database engine optimizations } else { # Use standard SQL } }
On Tue, 10 Dec 2002, Chris Cormack wrote:
The technical constraint is the actual issue, and im not against binding koha to specific db in principle. If the benefits gained are such to warrant the disadvantages.
I'll just restate my opinion here as well -- I think that tying ourselves to MySQL is ok (if we win enough by doing so), we should do our best to make migrating to another DB as easy as possible if we do so though. -pate
Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
Pat Eyler a écrit:
On Tue, 10 Dec 2002, Chris Cormack wrote:
The technical constraint is the actual issue, and im not against binding koha to specific db in principle. If the benefits gained are such to warrant the disadvantages.
I'll just restate my opinion here as well -- I think that tying ourselves to MySQL is ok (if we win enough by doing so), we should do our best to make migrating to another DB as easy as possible if we do so though.
nice to read pate and chris almost at the same time :-) * good night to chris * good morning to pate * good ... lunch to me :-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIBGB libre http://fr.koha.org)
participants (4)
-
Chris Cormack -
Francisco M. Marzoa Alonso -
Pat Eyler -
paul POULAIN