Re: plug-n-play MS SQL Server replacement - Mailing list pgsql-advocacy

From Christopher Browne
Subject Re: plug-n-play MS SQL Server replacement
Date
Msg-id m3ad3dqs18.fsf@wolfe.cbbrowne.com
Whole thread Raw
In response to plug-n-play MS SQL Server replacement  ("Lane Beneke" <lane.b@smcinc.com>)
Responses Re: plug-n-play MS SQL Server replacement
List pgsql-advocacy
Quoth josh@agliodbs.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

pgsql-advocacy by date:

Previous
From: Josh Berkus
Date:
Subject: Re: plug-n-play MS SQL Server replacement
Next
From: David Costa
Date:
Subject: Question