Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Informal Survey on Databases 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 1. I often use SQLite for prototyping and then throw the prototype away and re-write in MySQL or Oracle. I've only once ported a working application from one db to another though, and that was Access to MS SQL Server.

    2. Whenever I have seperate applications writing to the database, they're pretty much always just seperate wrappers around a library - eg, a GUI front-end and a command-line front-end.

    3. I try not to use DB-specific features, at least in low-end databases like SQLite and MySQL, on the (almost certainly spurious) grounds that I might upgrade later without re-writing the app. Writing overly-portable code is a bad habit of mine. I don't particularly mind using DB-specific features for high-end databases like Oracle though, as the probability of ever moving is so low. And anyway, you usually choose Oracle precisely for its proprietary features.

    4. Yes, but the real reason was poor documentation. What they did was correct by the docs.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.