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

[ psqlodbc-Bugs-1000507 ] MSSQL syntax

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1000507 ] MSSQL syntax
Date: 2005-12-27 09:01:10
Message-ID: 20051227090110.C080D112507E@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-odbc
Bugs item #1000507, was opened at 2005-12-27 02:23
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000507&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: MSSQL syntax

Initial Comment:
MSSQL have a command that Postgresql don't support:

@@spid

This command returns MSSQL connection pid.

I've a application that uses this query. I can't change code, but i need that psqlodbc ignore this command.

----------------------------------------------------------------------

>Comment By: Ludek Finstrle (luf)
Date: 2005-12-27 10:01

Message:
I don't know if we want this behaviour. When you move to other DB do you think they will add support for this?

I need to talk about it with other developers. I'm againist this kind of support.

@@spid is whole command or is it located inside statements?

If you're a little bit familiar with C you can hack it into psqlodbc code yourself (I think in PGAPI_Prepare and PGAPI_ExecDirect).

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2005-12-27 02:25

Message:
can psqlodbc to transform all "@@xyz" syntax in:

xyz()

?????

----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000507&group_id=1000125

pgsql-odbc by date

Next:From: Ludek FinstrleDate: 2005-12-27 09:11:50
Subject: for psqlodbc developers: [ psqlodbc-Bugs-1000507 ] MSSQL syntax (fwd)
Previous:From: noreplyDate: 2005-12-27 08:49:32
Subject: [ psqlodbc-Bugs-1000506 ] Not all ODBC-Standard-Calls work correctly

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