Jeroen Ruigrok van der Werven wrote: > Nikki, > > On 1/15/06, nikki <[EMAIL PROTECTED]> wrote: > > I kinda laughed that naively I stepped on a sore spot about choice of > > DB's but honestly it only reflect info I came accross , not an attempt > > to insult anyone - sorry John -I'm still not sure of the implication of > > my question. I know Rails supposedly works well with them all and even > > .net can work with mySql. Again thanks Adrian for taking the time I > > know in this community you are the Man - I appreciate your time > > You will find most people here are quite database agnostic, but if you > ask any DBA (database administrator) worth his/her value they will not > even consider MySQL. If you need features on an enterprise level, i.e. > compete with Oracle or Microsoft SQL Server, you will come to > PostgreSQL, not MySQL. > At one point, I am not sure they still do this, MySQL even altered > column types if it thought it would speed up the database, which is > all nice and dandy, but a death sin for any serious DBA. > > But that's digressing from what you asked. > > Depending on what you need for your installation you might even get > away from SQLite. I find this document is fairly good reading about > considerations what to use and when: > http://www.sqlite.org/whentouse.html. > > -- > Jeroen Ruigrok van der Werven
Ok your take is appreciated since it is somewhat different then the common mis?understanding. The common lore on MySQL is that its good enof for Google, Yahoo, Amazon so its a contender. SQLite I'm told does not support concurrent users very well. Also I came accross this DB comparison chart as of 3/05: http://www.geocities.com/mailsoftware42/db/ which may interest you
