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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 1. How often have you ported an app from one database engine to another (e.g., MySQL to Oracle)?

    A fair number of times. Must be a dozen or so in the last 10 years. Once already this year and it's only February - and this was the second time that this particular application had it's database changed from underneath it.

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

    A significant minority of applications.

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

    Often.

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

    Occasionally.

    About as many times as I've had people damaging data by going around the logic in the database layer. Some dumb ass will always find a way to damage data if that's what they're trying to do :-)

    Personally I think the location of the business logic depends more on the application, the development team, how it's going to be supported, the size of the application, amount of development time, responsiveness of the DBA, etc. than on more abstract issues of technical merit.

    If I've got an application that's talking to a large corporate database used by three other 24x7 applications written in a combination of four different development languages then I'm going to stick the business logic down in the database layer.

    If I've got an intranet tagging tool that's being developed for a single department, a technology development path that means we're going to be switching databases in 18 months, rapidly changing requirements and a database department with a 15 working day turn around on change requests then I'm going to put the business logic in the application layer.