Re^2: Determining if SQLite db exists

Mostly good advice, though I'd add this caveat: Matt probably wouldn't and shouldn't change the default behaviour. There are lots of scripts out there that depend on the automatic database creation. I suppose the best way (if it belongs in the module at all) would be to allow users to pass a "sl_no_db_create" attribute in connect() that would trigger the die on non-existant database behaviour

Comment on Re^2: Determining if SQLite db exists

Replies are listed 'Best First'.
SQLite (or other module) feature additions by ChemBoy (Priest) on Feb 28, 2005 at 17:29 UTC
An excellent point, to which I would only add that producing a patch to implement such a flag would almost certainly greatly enhance its likelihood of being included in a future release. (Why yes, I'm having a jargon-heavy day at work, why do you ask?) If God had meant us to fly, he would never have given us the railroads. --Michael Flanders	[reply]
Re^3: Determining if SQLite db exists by jfroebe (Parson) on Feb 28, 2005 at 17:09 UTC
I totally agree :) Setting an attribute for this behavior would be best - if such a change to DBD::SQLite were to be made Jason L. Froebe Team Sybase member No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1	[reply]