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

Re: How can I keep an OdbcDataAdapter from using fully qualified tble names?

From: Rob Richardson <interrobang(at)yahoo(dot)com>
To: Barry Bell <Barry_Bell(at)harte-hanks(dot)com>, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: How can I keep an OdbcDataAdapter from using fully qualified tble names?
Date: 2012-04-25 14:52:40
Message-ID: 1335365560.94781.YahooMailRC@web83606.mail.sp1.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-odbc
The issue is that ADO.Net's OdbcDataAdapter object automatically expands the 
table name "MyTable" into "MyDatabase.public.MyTable", and PostgreSQL cannot 
handle that.

In PgAdmin, "insert into cycle (cycle) values ('Another cycle')" succeeds, but 
"insert into Anneal.public.cycle (cycle) values ('Another one')" fails with the 
cross-database references not implemented error.  The OdbcDataAdapter object 
automatically converts a query of the first form into a query of the second 
form, and I want to know how to stop it from doing that.

RobR

In response to

Responses

pgsql-odbc by date

Next:From: Nils GöscheDate: 2012-04-25 15:02:01
Subject: Re: How can I keep an OdbcDataAdapter from using fully qualified tble names?
Previous:From: Barry BellDate: 2012-04-25 14:35:11
Subject: Re: How can I keep an OdbcDataAdapter from using fully qualified tble names?

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