in reply to How aggressive is your database leverage in application development?

I think you go over the line when you start coding application logic into the database itself. That is, unless you are coding those business rules on top of a separate and well defined entity/relation model.

But I can't really think of a good reason except for extreme performance demands to implement application logic in the DB, at least until someone embeds Perl, or something like it in a database, along with a reasonable interface. Situations requiring complex database operations and near realtime performance a the same time are pretty rare.

  • Comment on Re: How aggressive is your database leverage in application development?

Replies are listed 'Best First'.
Re^2: How aggressive is your database leverage in application development?
by james2vegas (Chaplain) on Apr 27, 2010 at 19:44 UTC
    Application logic and business rules are not the same thing. Business rules would need to be enforced on the data irrespective of the application accessing it. And as for Perl in the database, may I introduce you to PLPerl.

    I may be biased, I am a DBA first and programmer second, my preferred 'ORM' would be using stored procedures in the database when executing object methods, like DBIx-ProcedureCall
[reply]

In Section Meditations