On Jan 24, 2013 2:53 AM, "Federico Strati" <fede.str...@gmail.com> wrote: >... > The proposed idea is in its very early stage of conception, so any discussion, > even if completely against it (but with good reasons), will be appreciated > as well as any pointer to related on going efforts in any project.
IMO, RDBMS independence is a useless goal. Software deployments never wake up on a Thursday, and say, "let's change our database." Always, the goal is to store information, and to make the best use of the subsystem. This means you take advantage of RDBMS specifics. So this *really* means you're not changing the backend. I have never seen a valid use case for a true, production system needing a switchable backend. Similar API? Sure. But not exactly the same. The best apps will design for a specific backend, and will need specific API access. The proposed concept of query abstraction across "paths" (whatever) goes even further away from proper app/db design. Cheers, -g
