> > > Database independence is a fallacy. > > > > +1 to that. > > No it's not. With the proper O/R mapper, true db independence is a > reality.
+1 to _THAT_. I'm using WilsonORMapper (and have used nHibernate and hand-rolled ones too -- sorry Frans) and my application is totally DB agnostic. It has to be because we have to deploy on [IIS/ASP.Net/SQL Server], [IIS/ASP.Net/Oracle] and on [Apache/Mono/ASP.Net/MySQL]. For CRUD/Transactional stuff, this is a no-brainer. What DOES need brain-power is defining views for the mining/reporting queries, but that's truely a DB specific activity anyway, since it is so dependant on the data in-use. Our application is "mostly" shrink-wrap. -- "Under capitalism, man exploits man. Under communism, it's just the opposite." –John Kenneth Gailbraith Marc C. Brooks mailto:[EMAIL PROTECTED] http://musingmarc.blogspot.com
