Opened 14 years ago
Closed 13 years ago
#1471 closed defect (fixed)
Mapguide Maestro 2.1. Validating a layer based on a view does not always work
Reported by: | gabrimonfa | Owned by: | jng |
---|---|---|---|
Priority: | low | Milestone: | Maestro-3.5 |
Component: | Maestro | Version: | 2.1.0 |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description
Mapguide Maestro 2.1.4
Some views are reported as missing in the feature source even if they are found and correctly used by Mapguide 2.1 & 2.2. I'm using OGR Provider and PostgreSQL 8.3 (gdal recompiled to connect to PostgreSQL/PostGIS). Some other instead are reported as correct.
Apparently it doesn't matter if a field in the view is of type integer and has unique values
Attachments (5)
Change History (11)
comment:1 by , 14 years ago
Milestone: | → Maestro-3.0 |
---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
I'm using gdal 1.7.2 (from SVN stable), enabling PostgreSQL/PostGIS support
I've compiled it on centos 5 i386. This is configuration report:
GDAL is now configured for i686-pc-linux-gnu
Installation directory: /usr/local
C compiler: gcc -g -O2
C++ compiler: g++ -g -O2
LIBTOOL support: yes
LIBZ support: external
GRASS support: no
CFITSIO support: no
PCRaster support: internal
NetCDF support: no
LIBPNG support: internal
LIBTIFF support: external (BigTIFF=no)
LIBGEOTIFF support: internal
LIBJPEG support: external
8/12 bit JPEG TIFF: no
LIBGIF support: internal
OGDI support: no
HDF4 support: no
HDF5 support: no
Kakadu support: no
JasPer support: no
ECW support: no
MrSID support: no
MSG support: no
GRIB support: yes
EPSILON support: no
cURL support (wms/wcs/...):yes
PostgreSQL support: yes
MySQL support: no
Ingres support: no
Xerces-C support: no
NAS support: no
Expat support: no
ODBC support: no
PGeo support: no
PCIDSK support: internal
OCI support: no
GEORASTER support: no
SDE support: no
DODS support: no
SQLite support: no
SpatiaLite support: no
DWGdirect support no
INFORMIX DataBlade support: no
GEOS support: no
VFK support: yes
SWIG Bindings: no
Statically link PROJ.4: no
enable OGR building: yes
enable pthread support: no
hide internal symbols: no
Then I installed it in /usr/local/lib and symlinked it in /usr/local/fdo-3.5.0/lib/libgdal.so.1
I've verified that
ldd /usr/local/lib/libgdal.so | grep not
ldd -r /usr/local/lib/libgdal.so | grep undefined
are empty (no missing symbols & libraries) and that
ldd /usr/local/lib/libgdal.so | grep pq
libpq.so.4 => /usr/lib/libpq.so.4
(PostgreSQL support is indeed enabled) and that
ldd libOGRProvider.so | grep gdal
libgdal.so.1 => /usr/local/fdo-3.5.0/lib/libgdal.so.1
and that
ls -l /usr/local/fdo-3.5.0/lib/libgdal.so.1
/usr/local/fdo-3.5.0/lib/libgdal.so.1 -> /usr/local/lib/libgdal.so
and that
ldd libOGRProvider.so| grep not
ldd -r libOGRProvider.so| grep undefined
are empty
Thus no undefined symbols everywhere
My libgdal.so.1.14.2, renamed to libgdal.so for your convenience, is attached
by , 14 years ago
Attachment: | libgdal.so.zip_00 added |
---|
The zip file is obtained with cat libgdal.so.zip_* > libgdal.so.zip
by , 14 years ago
Attachment: | libgdal.so.zip_01 added |
---|
by , 14 years ago
Attachment: | libgdal.so.zip_02 added |
---|
by , 14 years ago
Attachment: | libgdal.so.zip_03 added |
---|
by , 14 years ago
Attachment: | libgdal.so.zip_04 added |
---|
comment:4 by , 14 years ago
Milestone: | Maestro-3.0 → Maestro-3.1 |
---|
comment:5 by , 14 years ago
Milestone: | Maestro-3.1 → Maestro-3.5 |
---|
comment:6 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Closing due to ticket inactivity. Assumed fixed with newer releases
Could you attach this custom OGR provider binary?