Hi Adam, I put this code in a separate module because
a) very few people will ever use it (only some of the people who already used FTS3 in previous versions) b) for people who will use it, it will be probably a one-shot operation (to update their code). so inserting this functionality for ever into the main module doesn't sound so good to me. What could be done, however, is to remove it completely from the DBD::SQLite distrib and pack it into a separate distribution; so only people who really need that stuff will install it. Laurent Dami >-----Message d'origine----- >De : Adam Kennedy [mailto:adamkennedybac...@gmail.com] >Envoyé : mardi, 7. septembre 2010 05:46 >À : SQLite Mailing List >Objet : [DBD-SQLite] FTS3Transitional.pm > >Before I push the new release, I have a couple of questions about the >FTS3Transitional.pm file. > >Do we really want this as a different module? It's got a tiny amount >of simple code with no dependencies, uses Exporter, disables a >warning, and generally doesn't behave like the rest of the code. > >Is it really needed to have this as a separate module, or could we >just roll the function into DBD::SQLite somewhere as a utility >function? > >If we can easily fit it into our current API, I'm mildly against >adding more surface area and different API modalities if we can avoid >it. > >Adam K > >_______________________________________________ >DBD-SQLite mailing list >DBD-SQLite@lists.scsys.co.uk >http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite _______________________________________________ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
