Missing write acces to PostGres using Postgres ODBC ver. 9

[Bo Victor Thomsen]

To the list -

I'm experiencing problems using the Postgresql ODBC driver ver. 9.00.
When I use this driver, my Postgresql based tables becomes read-only. If
I use the Postgresql 8.4 ODBC driver with the exact same setup, the
tables are read/write. (To answer the obvious question: Why don't I keep
using the 8.4 driver ? - MapInfo and the MapBasic application is
situated on a Citrix server where corporate IT is a very tough dance
partner - and they are using Postgresql ODBC ver. 9.00) .

The configuration:
Database: Postgresql 9.0 / Postgis 1.5
MapInfo version: 10.0 with patches. (Using MapInfo ver. 11 doesn't
change the read-only situation)
Tables are directly connected (not linked) to the postgres tables with
cache. Not using cache doesn't change the read-only situation
All tables are registered in the MapInfo_Mapcatalog table and all tables
has a numeric primary key.

Has anyone a workaround for this problem ?

Regards

Bo Victor Thomsen
Aestas
Denmark

[Peter Horsbøll Møller]

Hi Bo,

Has the v9.00 ODBC driver been configured in the exact same way as v8.4 ODBC driver?

I do recall that MI Pro had a similar issue with another earlier version of the ODBC driver

Could the issue be that MI Pro - for some reason - can't locate the primary index in the tables?

Does it help if you rename the primary index column to MI_PRINX?

 
Peter Horsbøll Møller
Pitney Bowes Business Insight - MapInfo

2011/11/1 Bo Victor Thomsen <bo.victo...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.To post a message to this group, send email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en

[Bo Victor Thomsen]

Hi Peter -

I've used the exact same procedure when I tried to connect to the database table using different ODBC drivers:

1. Open a DBMS connection using either xxx84.dsn (ver. 8.4) or xxx90.dsn (ver. 9.0)
2. Open a tab - file by setting the appropriate connection type, i.e  "PostgreSQL:1" and choosing a database table from the list.
3. Create a tab file for the chosen table as a direct connection with cache enabled.
   

I have attached the two dsn files and the resulting tab files to this post.
The table has a numeric primary key already named "mi_prinx" (see the attached "vand.sql" script)
The database user "postgres" is a superuser and has all rights to the database
Both ODBC drivers has connection pooling enabled.

There is two differences in the attached tab files (apart from the driver name):

1. The line "\DATALINK\MapReadOnly" = "TRUE" appears in the metadata section of the version 9.0 tabfile. It is not present in the 8.4 version. But removing this line - or changing it to FALSE - doesn't change the read-only problem.
2. The connection string for ver. 9.0 tab-file contains an extra parameter: GssAuthUseGSS=0; AFAIK, It's disabling GSS authentication.
   

I simply can't get a grip on this problem :-/

Has anyone connected MapInfo to a Postgres database with read/write capabilities using Postgres ODBC ver. 9.0 ?

Regards

Bo Victor Thomsen
Aestas
Denmark

[Richard Greenwood]

Bo,

Hopefully you have found an answer to this post by now, but one thing
that I have found is that you can make a read-only postgis table
editable by making a copy of it. For example:
create new_table as select * from existing_table;
You must then manually enter a row in the mapinfo_mapcatalog for the new_table.

If you have found another solution please let us know. It seems like
there is quite a bit of trial and error involved with MapInfo access
to PostGIS tables.

Rich

--
Richard Greenwood
richard....@gmail.com
www.greenwoodmap.com

[Quentin]

Hello,

I had the same problem, the answer from MapInfo (and also stated in their manuals) is that they dont support PostGIS ODBC-drivers above version 8.4.

Regards
Ulrik