December 2008 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Mon Dec 1 09:10:57 EDT 2008
Ending: Mon Dec 15 16:28:02 EDT 2008
Messages: 34

• [fdo-trac] #269: SHP: read only files causes problem for spatial queries   FDO
• [fdo-trac] #278: Update GDAL version to 1.6.x   FDO
• [fdo-trac] #278: Update GDAL version to 1.6.x   FDO
• [fdo-trac] #348: Port to VS2008   FDO
• [fdo-trac] #352: ArcSDE 9.2 globalid field type support   FDO
• [fdo-trac] #352: ArcSDE 9.2 globalid field type support   FDO
• [fdo-trac] #372: ArcSDE: Cannot connect using ArcSDE 9.2   FDO
• [fdo-trac] #373: WMS: Cannot handle an url with that ends with character "?"   FDO
• [fdo-trac] #378: ODBC: De-referencing a NULL ptr for select aggregate   FDO
• [fdo-trac] #412: ArcSDE: dbo user is not supported   FDO
• [fdo-trac] #412: ArcSDE: dbo user is not supported   FDO
• [fdo-trac] #416: Change to version 3.4   FDO
• [fdo-trac] #422: FDO Filter to SQL statement process optimization for RDBMS   FDO
• [fdo-trac] #426: ArcSDE: Add Windows authentication   FDO
• [fdo-trac] #428: SQL Server Spatial Provider: Incorrect sequence to determine coordinate system data   FDO
• [fdo-trac] #437: Georaster Oracle 11g support in FDO   FDO
• [fdo-trac] #438: RDBMS: Handle circular association properties   FDO
• [fdo-trac] #438: RDBMS: Handle circular association properties   FDO
• [fdo-trac] #439: FDO API Managed, SQLServerSpatial managed/unmanged docs are missing from the Linux build   FDO
• [fdo-trac] #439: FDO API Managed, SQLServerSpatial managed/unmanged docs are missing from the Linux build   FDO
• [fdo-trac] #439: FDO API Managed, SQLServerSpatial managed/unmanged docs are missing from the Linux build   FDO
• [fdo-trac] #440: Ticket for RFC 29   FDO
• [fdo-trac] #440: Ticket for RFC 29   FDO
• [fdo-trac] #440: Ticket for RFC 29   FDO
• [fdo-trac] #441: SQLServerSpatial: Propogate up connection errors   FDO
• [fdo-trac] #441: SQLServerSpatial: Propogate up connection errors   FDO
• [fdo-trac] #441: SQLServerSpatial: Propogate up connection errors   FDO
• [fdo-trac] #442: Change the version info to be more consistent   FDO
• [fdo-trac] #442: Change the version info to be more consistent   FDO
• [fdo-trac] #443: PostGIS defect : Only 1 geometry column of a table can be used   FDO
• [fdo-trac] #443: PostGIS defect : Only 1 geometry column of a table can be used   FDO
• [fdo-trac] #444: WMS Provider GetMap drops exception information   FDO
• [fdo-trac] #444: WMS Provider GetMap drops exception information   FDO
• [fdo-trac] #444: WMS Provider GetMap drops exception information   FDO

Last message date: Mon Dec 15 16:28:02 EDT 2008
Archived on: Mon Dec 15 16:28:04 EDT 2008

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...