This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Preferred databases
Feed Title: David Buck - Blog
Feed URL: http://www.cincomsmalltalk.com/rssBlog/buck-rss.xml
Feed Description: Smalltalk can do that
It stricks me as odd that Microsoft created two completely different sets of classes to interface to databases. One set is optimized for SQL Server and the other is generic for any database accessible by ODBC. The consequence of this is that developers typically write code for one or the other (most often SQL Server). They start referencing all the SQL Server classes from all over their code, passing back SQL Server classes as return types, and storing them in variables. If they then need to change databases, it's virtually impossible to do.
I believe that high level applications shouldn't care what the database is and it should be possible (with some small amount of effort) to change the database without making large scale changes to the application.
Sadly, the .NET environment doesn't seem to encourage this. It seems like it's Microsoft's way of bringing you into their world then locking you in.
Previous Topic
