From: | Shelby Cain <alyandon(at)yahoo(dot)com> |
---|---|
To: | James Harper <james(dot)harper(at)bendigoit(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transact SQL compatibility layer |
Date: | 2006-01-23 18:07:20 |
Message-ID: | 20060123180720.75371.qmail@web50113.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- James Harper <james(dot)harper(at)bendigoit(dot)com(dot)au> wrote:
> Is there such a thing as a translator/proxy that can pretend to be a
> Microsoft SQL server and proxy all the commands to a PostgreSQL
> server,
> and the results back again? Obviously the purpose of it would be to
> allow an application written for MSSQL Server to work with PostgreSQL
> without modification.
>
> If not, has such a thing been considered? What would be the obstacles
> to
> developing such a proxy?
>
Assuming your goal is compatibility to a level such that no changes are
required in the client application, I'd say it'd be a tremendous amount
of work. At the very least you'd have to reverse-engineer mssql
server's communication protocol and write a proxy that could understand
and translate that to something compatible with postgresql. Then you'd
have to deal with the difference between the two server sql dialects.
All in all, you'd be much better off designing your application such
that it explicitly supports multiple databases to begin with.
Regards,
Shelby Cain
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-01-23 18:50:06 | Re: Transact SQL compatibility layer |
Previous Message | Tom Lane | 2006-01-23 17:40:59 | Re: invalid memory alloc request size |