Re: [Fwd: MS SQL compatible functions] - Mailing list pgsql-general

From Steve Boyle \(Roselink\)
Subject Re: [Fwd: MS SQL compatible functions]
Date
Msg-id 006701c1afee$16387300$55b36bd5@dualtower
Whole thread Raw
In response to Re: [Fwd: MS SQL compatible functions]  ("Ian Harding" <ianh@tpchd.org>)
List pgsql-general
Hi Justin,

Just saw this on the newsgroup.

I think it would be interesting to do some gap analysis (apologies for the
management talk) that identified what could be done in MSSql server that
cannot be done in postgres and use that to:

a:    provide functional comparison material to allow people to make a more
informed decision when selecting there db.
b.    drive out potential projects to aid and encourage migration.

I probably won't have much time to get involved in this over the next
coiuple of months but may be able to get involved later.

any thoughts?

regards

steve
----- Original Message -----
From: "Justin Clift" <justin@postgresql.org>
To: "Ian Harding" <ianh@tpchd.org>; "PostgreSQL Hackers Mailing List"
<pgsql-hackers@postgresql.org>
Cc: <pgsql-general@postgresql.org>; <dean@tmdt.com.tw>
Sent: Wednesday, February 06, 2002 11:42 PM
Subject: Re: [GENERAL] [Fwd: MS SQL compatible functions]


> Hi Ian,
>
> A compatibility has already been considered for Oracle, you're
> mentioning one for MS SQL Server.
>
> Maybe it's time to think about how an abstraction layer could be added,
> and then appropriate Oracle/Sybase/Informix/MSSQL/etc
> modules/plug-ins/layers could be added to that?
>
> Wonder how much work it would take?
>
> :-)
>
> Regards and best wishes,
>
> Justin Clift
>
>
> Ian Harding wrote:
> >
> > This is something that would be wonderful to have, a mapping of
PostgreSQL functions to MSSQL Server functions.  In fact, I have been
fantasizing about a compatibility module that would allow SQL Server
applications to think they were talking to MSSQL Server when they were
really talking to PG.  That is a huge job, but my how many more people would
convert!
> >
> > In the meantime, you will have to dump schema, twiddle them to meet
PosgtreSQL requirements, and run them to re-create your db.  Your app will
have to be re-written to some degree as well.
> >
> > Ian A. Harding
> > Programmer/Analyst II
> > Tacoma-Pierce County Health Department
> > (253) 798-3549
> > mailto: iharding@tpchd.org
> >
> > >>> Justin Clift <justin@postgresql.org> 02/06/02 02:31AM >>>
> > Hi everyone,
> >
> > Dean here seems to be converting to PostgreSQL from MS SQL Server, and I
> > have *no* idea how to help him out.
> >
> > He's not on the list, so if anyone's got suggestions, please remember to
> > keep him in the To/CC list.
> >
> > :-)
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > -------- Original Message --------
> > Subject: MS SQL compatible functions
> > Date: Wed, 6 Feb 2002 18:17:13 +0800
> > From: "Dean Lu" <>
> > To: <justin@postgresql.org>
> >
> > Dear Justin,
> >         My name is Dean Lu, I am working in a SI company in Taiwan, we
are
> > going to change our products to support the PostgreSQL and drop the MS
> > SQL away, but I got some problems with the functions compatibility
> > between MS and pgSQL. Could you please give me some suggestions or tell
> > me where can I get the functions from Internet. It will be better if
> > those functions are written in C language. Thank you very much.
> >
> > Best Regards'
> > Dean Lu
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
> --
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
>    - Indira Gandhi
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>


pgsql-general by date:

Previous
From: Jeff Eckermann
Date:
Subject: Re: Build problems with 7.2
Next
From: Mike Barrett
Date:
Subject: Inserting Default Values