This goes along with my other email about modularizing
authentication. My feeling is that most of koha is sort of embedded, like
auth the storage should be modularized, like this
there should be a wrapper with default methods that
do something a default way, one of those would be search. the mysql search
would use mysql features (ie: full text search), a postgres search would
do whatever they do. basically you'd have custom queries for each DBM since
each method that does the querying would be DBM specific. Only the parent
class would hold static variables and things that would be consistant across
all the DBM's. If done this way storage is trivial, one could store everything
in flat text files if they wanted!.
I must emphasize that this is the *correct* way to
program things like this, and if we (my university) decides to use Koha
I will certainly help wherever i can.
That's it, i have understood what you meaned yesterday, with this mail.