From the docs:
Hey, how'd you know about that fix I found? Oh right, you invented it. :)
Thanks a million, Frank -- you're worth twice your weight in gold. Even
just telling me to go hack it myself, actually got the job done, and I
learned a bit about the internals of OGR+ODBC.
--
HostGIS,
Gregor at HostGIS wrote:
Hey, this is so excellent. I took Frank's advice about just trying to
hack the C++ code... and discovered as a side effect that FreeTDS has a
new release. This new release fixed the issue. Ha!
I do have one outstanding issue, though: it is very, very, very, very
slow
Hey, this is so excellent. I took Frank's advice about just trying to
hack the C++ code... and discovered as a side effect that FreeTDS has a
new release. This new release fixed the issue. Ha!
I do have one outstanding issue, though: it is very, very, very, very
slow because it scans every tab
Frank Warmerdam wrote:
> Debuging MS SQL related bugs isn't really all that convenient for me
Ha ha! I myself rank any dealing with MS SQL on par with cleaning the
Augean Stables. I understand. :)
You could add some debug statements in the
gdal/port/cpl_odbc.cpp code in an attempt to determi
Gregor at HostGIS wrote:
Hey guys. I posted a few days ago about a problem with using ogrinfo to
read ODBC from a MS SQL server.
$ ogrinfo test.ovf
ERROR 1: No column definitions found for table
'�o��y.����y', layer not usable.
(... and so on, more binary table names ...)
I can
Hey guys. I posted a few days ago about a problem with using ogrinfo to
read ODBC from a MS SQL server.
$ ogrinfo test.ovf
ERROR 1: No column definitions found for table
'�o��y.����y', layer not usable.
(... and so on, more binary table names ...)
I can connect to the ODBC/MSSQL
Hey guys. A few weeks back, Chaitanya helped us out with some fixes
regarding unixODBC on 64-bit platforms, and got MapServer able to render
remote data via ODBC from PostgreSQL and MySQL. Thanks a million!
Now we're on the last step: getting OGR data sources to work when the
ODBC server is Mi
