Thank you for the suggestion; again something I did not think of (!)...
So I tried some really 'easy' little datasets; points with some INT
attributes. Still no luck, though...
It seems that MapInfo v10 is not compatible with PostGIS 1.4.0. This makes
me wondering, having the error message in mind ("Unable to translate the
Spatial Constraint."): is this spatial constraint expressed differently in
PostGIS 1.4.0 , comparing it to, say, 1.3.5? One could even think of even
very small differences like capitals in functions e.g. st_srid() versus
ST_srID() etc. etc. At least success has been reported (by some other users,
like you Richard) of working with PostGIS (1.3.5 or lower) from MapInfo...
Does any one have a clue?
Rob
2009/10/6 Richard Greenwood <richard.greenw...@gmail.com>
> Just for the record - I have MapInfo Live Access (not cached) working
> nicely with MI 10.0, pgsql 8.3.6, PostGIS 1.3 on a mixed geometry
> table (multi-polygons & points) of about 14000 rows. Attribute queries
> are disappointingly slow, but map rendering is very fast.
>
> --
> Richard Greenwood
> richard.greenw...@gmail.com
> www.greenwoodmap.com
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
