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.

  • Response. (Score:1)

    by jarich (4909) on 2006.02.18 19:52 (#46205) Homepage Journal

    1. How often have you ported an app from one database engine to another (e.g., MySQL to Oracle)?

    Once in 8 years.

    2. How often have you had completely separate apps writing to the same data store (using completely different code bases)?

    About a dozen (still maintained) projects.

    3. Do you depend on non-portable database features?

    It depends. Beyond default values, not nulls, primary keys, foreign keys, autoincrement and constraints (cascade delete...) I generally don't encode business logic in the database. Nevertheless even this isn't very portable.

    I also use database functions such as "NOW()" and date formats which all seem to vary across databases, although I try to use standards where they exist.

    4. Have you experienced programmers damaging your data because the logic wasn't in the database layer?

    Never.

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