Re: Supporting multiple databases without code change - Thanks

[Hrayr Galoyan]

Just wanted to say thanks for your comments, guys.

Hrayr

"Hrayr Galoyan" <hrayr@systronics.com> wrote:
>
>Hi,
>
>We are writing a large banking application and would like to support multiple
>databases (Pervasive, MS SQL, Oracle). Initially, we thought we would have
>a separate Data Access Layer, but later dropped the idea since it was not
>clear what exactly should that layer contain.
>
>What we decided was to use only the basic features of databases. We will
>not use stored procedures, views, not even foreign keys. All the validations
>will be done in Business Logic layer. The idea is that basic SQL syntax
must
>be the same in all major databases, so theoretically our code should run
>without changes. We only need to provide a connection object that points
>to a different database.
>
>If you have experience in similar implementation, please let me know what
>are the possible dangers. Anyway, what do you think about this approach?
>How to define the "basic SQL syntax" to be safe?
>
>Will be glad to hear any opinion.
>
>Hrayr Galoyan