How can I keep an OdbcDataAdapter from using fully qualified tble names?
От | Rob Richardson |
---|---|
Тема | How can I keep an OdbcDataAdapter from using fully qualified tble names? |
Дата | |
Msg-id | 1335362750.25657.YahooMailRC@web83604.mail.sp1.yahoo.com обсуждение исходный текст |
Ответы |
Re: How can I keep an OdbcDataAdapter from using fully
qualified tble names?
Re: How can I keep an OdbcDataAdapter from using fully qualified tble names? |
Список | pgsql-odbc |
Hello! How can I keep an OdbcDataAdapter from insisting on the fully qualified table name? In VS 2008, I am trying to use the System.Data.Odbc namespace to work with a PostGres database. I don't want to use npgsql because I want to work with DSNs so that I get the flexibility of changing databases without changing my program. When I use an OdbcCommandBuilder object to create the insert, update and delete commands for me, the table names are fully qualified. For example, an insert command might begin with "insert into MyDatabase.public.MyTable...". When I try to use that, I get an exception thrown that complains that cross-database references are not implemented (even though the connection I am using is to the MyDatabase database). So, I wrote a little function that converts a string containing "MyDatabase.public.MyTable" into "MyTable", and use that to replace the fully qualified name in the command text with the bare table name. But when it comes to time to call the adapter's Update() method to add a new row into my table, the first thing the adapter does is to change the bare table name back to the full "MyDatabase.public.MyTable" name, and then I get the same exception. Thank you very much. RobR
В списке pgsql-odbc по дате отправления: