Andrew Piskorski wrote:
We have an enterprise application that we host, and we needed to write a desktop version that executives could use on planes, etc. Being able to easily change from postgresql to sqlite was a big help in getting that done. It is a little extra work(only a little) to be generic, but with some wrapper functions, its worth a lot more than the trouble you might run into by not doing it. Also PearDB for PHP has some nice wrappers for a variety of different databases, that make this simpler, and other languages would have similar(at least I think perl does).On Fri, Aug 27, 2004 at 05:30:40PM -0400, D. Richard Hipp wrote:
The best design would be to make the application generic so
that it could use either SQLite or a client/server database.
In an ideal world, yes. In practice... My guess is it's probably a
LOT more trouble than it's worth.
John LeSueur