I am designing a database framework (abstract back-end layer). I have to fulfill following requirements.
1) Can be used to configure with multiple database vendors (MS SQL, ORACLE)
2) Can't maintain multiple set of objects (stored procedures, views, functions) according to database vendors (ms sql, oracle, my sql )
I have experience of developing database abstract layer to support multiple database vendors by changing configuration files.
But i had to maintain different set of objects(sp's,views) each time before ,according to database vendor.
Now the situation is different, I am thinking a out of the box way to implement current scenario. If some one can give a good suggestion that would be really appreciated.
Thanks in advance,
Your question is essentially too broad for StackOverflow, but I recommend you stick to basic ansi sql, just select/update/insert/delete. Not even create statements or limit/top etc. Eventually maybe.
You only need to look at the sheer number of different ORM libraries out there to know that this is not an easy problem to solve in a particular way and there is no magic bullet or revolutionary thinking that will make it so. If there was, someone else would have done it- they haven't, they've just had teams of people writing massive libraries to cope with a highly varied task