From: | "George Weaver" <gweaver(at)shaw(dot)ca> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org>, "Rob Richardson" <interrobang(at)yahoo(dot)com> |
Subject: | Re: How can I keep an OdbcDataAdapter from using fully qualified tble names? |
Date: | 2012-04-25 15:12:03 |
Message-ID: | 98EDE81FC196430094E58830820A6828@D420 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
>----- Original Message -----
>From: Rob Richardson
>The issue is that ADO.Net's OdbcDataAdapter object automatically expands
>the table name "MyTable" into "MyDatabase.public.MyTable", and PostgreSQL
>cannot
>handle that.
I think you'll find that it is not ADO.Net's OdbcDataAdapter that expands
the table name, but
the CommandBuilder - I use ADO Net's OdbcDataAdapter extensively without
problem,
but I write my own OdbcCommands.
George
>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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2012-05-04 16:53:53 | Re: using pgsql-odbc using client certificate auth |
Previous Message | Nils Gösche | 2012-04-25 15:02:01 | Re: How can I keep an OdbcDataAdapter from using fully qualified tble names? |