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

Re: PostgreSQL / ODBC / Ms-SQL 2000

From: "Thomas Knoop" <Th(dot)Knoop(at)Talisma(dot)nl>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: PostgreSQL / ODBC / Ms-SQL 2000
Date: 2005-09-28 17:45:14
Message-ID: 200509281745.j8SHjC78038411@smtp-vbr13.xs4all.nl (view raw or flat)
Thread:
Lists: pgsql-odbc
 
Hi Dave,

First let me thank you for your input!

> > When I look at the properties of the linked server in Ms-SQL I can 
> > see that the catalog column is empty. I think MS-SQL expects a
> > (default?) value here,
> > and thats why we cannot proceed creating a view.
> 
> If SQL is expecting a value here even though the driver reports that 
> catalogs are not supported by the database then it's broken.
> I'll see if
> I can find some time to try to work out whats going on in the week. I 
> can't promise anything though.

> According the SQL docs, the correct syntax is something like:

> SELECT * FROM MYLINKEDSERVER..[public].mytable;

> However I can't get this to work. This does seem fairly common though, 
> with other users complaining of the same issues with Oracle. The commonly 
> suggested solution is to use:

> SELECT * FROM OPENQUERY(MYLINKEDSERVER, 'SELECT * FROM public.mytable')

> Which works perfectly afaict, apart from a minor issue with columns of 
> type 'name', for which I've just committed a fix to CVS.

As far I can see this tries to open the table complete, and fails in my case
cause i have a ADSL connection and it tries to fetch all the records....

This looks to me as a very slow workaround.

Regards,
  Thomas.



In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2005-09-28 18:10:50
Subject: Re: Problem with Cursor in Oracle from Postgresql via ODBC
Previous:From: HÃ¥kon ClausenDate: 2005-09-28 17:35:11
Subject: Re: ODBC driver types

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