Hey all. I've been asked to set up support for pseudo-spatial data via
ODBC. So far, I've not had any luck. We're using this as our starting point:
http://mapserver.org/input/vector/VirtualSpatialData.html
But I get this...
$ ogrinfo ODBC:gregor/mos...@testpgsql table
*** glibc detected *** free(): invalid next size (fast):
0x0000000000505520 ***
Aborted
So my very first questions are a) whether the tricks described in that
document has ever been considered production-stable, and b) whether
upgrading from GDAL/OGR 1.5.4 to 1.6.3 is likely to help. Then of course
(c) would be "So what AM I doing wrong?" :)
The OS is Linux, and I have installed unixODBC and drivers for
PostgreSQL (bundled with unixODBC) and MySQL (MySQL Connector). I then
rebuilt GDAL/OGR 1.5.4 including --withodbc=/usr/local/unixODBC
My odbc.ini is as follows:
[testPgSQL]
Description = Test to Postgres
Driver = PostgreSQL
Database = MY_DATABASE
Servername = MY_HOSTNAME
Port = 5432
Protocol = 8.2
ReadOnly = No
RowVersioning = No
ShowSystemTables = No
ShowOidColumn = No
FakeOidIndex = No
ConnSettings =
--
HostGIS, Open Source solutions for the global GIS community
Greg Allensworth - SysAdmin, Programmer, GIS Person, Security
Network+ Server+ A+ Security+ Linux+
PHP PostgreSQL MySQL DHTML/JavaScript/AJAX
"No one cares if you can back up — only if you can recover."
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
