Re: Searching OO Associations with RDBMS Persistence Models

What if we replace the database vendor? Must we rewrite all
the business rules?
What if we replace application programming language. Must we rewrite
all the business rules? Currently changes in programming languages are
more frequent than changes in database vendor. Nothing last for ever.
Besides there are a high level of standardization between database
vendors.

a DBMS is a bucket of bits with some low level rules to manage those bits.
How do you define low level? Lets say we have a business rule saying
that the customer name must be unique. Implementing this rule in a RDB
would need less lines of code than implementing the same thing in the
application. Normally something that takes few lines of codes is
considered high level, and something that takes a lot of lines of code
is considered low level.

We can completely eliminate the DBMS and replace it with
another of an entirely different form (non Relational for example) and
still have all the business behavior we need.
Of course, but it would take a lot more lines of code. The same could
be said about programming languages or software engineering
philosofies. We can completely eliminate it and replace it with another
of an entirely differnt form (non OO for example) and still have all
the business behavior we need.

that the database is the heart of the system. This is flawed. The heart of the
system is the application code
Someting the databse is indeed the heart of the system. Sometimes it is
not.

The database is a detail to be decided at the last possible moment and kept in a
position so flexible that it can be swapped out for another at a whim.
Why does the database need to be in a flexible position? Why does it
need to be swapped out at a whim?

Fredrik Bertilsson
http://frebe.php0h.com

.

Relevant Pages

  • Re: Data Layer architecture
    ... >>database theory are rather old, say, the 80-ies. ... A distributed DBMS might have parts located in the PCs, ... > foolish to implement the business rules in the applications. ... >>> Server is only an special kind of distributed system. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: OO vs. RDB challenge
    ... >> is a database independently of the representation. ... No a database is a set of data, not a representation of anything. ... I am talking about business rules as they are generally understood. ... Business rules are the constraints perceived by the end user and not ...
    (comp.object)
  • Re: Data Layer architecture
    ... >database theory are rather old, say, the 80-ies. ... A distributed DBMS might have parts located in the PCs, ... I readed several books about business rules and all of then say the ... >> Server is only an special kind of distributed system. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: "Business Logic / Rules should never be in the database or stored procedures"
    ... My primary role has served around the Oracle Applications environment and Oracle ... there exist a blend of business logic between the database and the application layer for ... Reason being that the database cannot process the business rules efficiently nor can they ... and do absolutely everything in the application layer. ...
    (comp.databases.oracle.misc)
  • Re: Business rules in stored procs.
    ... The second argument also ties your database design to one specific ... The last database that I worked on btw that was only accessed by one ... unless you want to replicate your business rules all over the place or end ... > the business rules in the same technology and tier. ...
    (microsoft.public.sqlserver.programming)