Skip site navigation (1) Skip section navigation (2)

Re: plug-n-play MS SQL Server replacement

From: Christopher Browne <cbbrowne(at)acm(dot)org>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: plug-n-play MS SQL Server replacement
Date: 2004-02-20 22:56:19
Message-ID: m3ad3dqs18.fsf@wolfe.cbbrowne.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
Quoth josh(at)agliodbs(dot)com (Josh Berkus):
> Also, if you have T-SQL procedures, you would have to somehow implement T-SQL 
> for Postgres; translating the procedures is really not an option.

You would be hit by a lot of other similar sorts of "impedances" to
those found with MySQL.  

Most conspicuously, MySQL is most likely an imitator of Sybase
(progenitor of the code that Microsoft sells) in having
"autoincrementing columns" as compared to PostgreSQL's notion of
"sequence objects."
-- 
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','ntlug.org').
http://cbbrowne.com/info/spreadsheets.html
Monday is an awful way to spend one seventh of your life.  -- Unknown

In response to

Responses

pgsql-advocacy by date

Next:From: David CostaDate: 2004-02-21 00:39:17
Subject: Question
Previous:From: Bruce MomjianDate: 2004-02-20 20:41:06
Subject: LinuxWorld Call for Papers - One Week Left (fwd)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group