[Oledb-dev] No binary output function available

[Clay, Bruce]

I am getting the same message that Uwe Seher mentioned back on 11 May.

 

I am using a combination of PostgreSql 8.0.3, postgis (version provided
in the PostgreSql 8.0.3 installer) and what I believe to be the current
PgOleDb dll.

 

I have loaded a few databases in PostgreSql and I can see the table
names in ArcCatalog after I make an OLE DB connection.

 

Two problems show up but I can not say at which level of the process
they occur.

 

The first is as the title says one that says:

 

Failed to edit the selected object(s)

General Function failure

ERROR: no binary output function available for type geometry

 

Fatal error in query.

 

 

The standard tables used by template1 all seem to open ok but the table
that has the actual data fails with the above error message

 

 

A data entry for one of the airport tables is as follows:

            0;0;0;1;"KOA";"Airport";"Kona International At
Keahole";1271744;"HI";"Hawaii
County";"15001";"15";"SRID=-1;POINT(-156.042831420898 19.7357311248779)"

 

All lines in the table use the same value for SRID and the last field is
of type geometry.

 

The second problem I encountered seems to be one of case sensitivity.
If a table has uppercase letters such as VE_SubProv I get the following
error message

 

Failed to edit the selected object(s)

General Function failure

            ERROR: relation "public.ve_subprov" does not exist.

 

            Fatal error on query

 

 

That would seem to imply that quotes are not used to tell PostgreSql to
maintain the input capitalization for tables.  Capitalization of
database names seems to work fine.

 

This second problem could be bypassed if we rename all of the tables to
use lower case letters as I did the one that gives the first error
message but I am using FIPS 10_4 codes within the database so it would
be nice to maintain the proper case if possible.

 

Any thoughts or suggestions would be greatly appreciated.

 

Thanks

 

Bruce

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/oledb-devel/attachments/20050526/9d2fad48/attachment.html