Rating: No reviews yet
Downloads: 98
Change Set: 24772
Released: Jun 28, 2013
Updated: Jun 28, 2013 by pkrejcir
Dev status: Stable Help Icon

Recommended Download

application, 1000K, uploaded Jun 28, 2013 - 98 downloads

Release Notes

There are two important changes in this PostGIS GDO release. The source code has been upgraded so that it gets compiled with the latest version of MinGW. The second change is that the most of the Database Utilities functionality has been moved into PsgDBUtils.dll which can be reused by 3rd party application to administer GDO metadata.

Fixed in this version
  • Fixed long term problem with occassionally unregistered dll or ocx
  • Fixed a memory leak on GRecordset object

Fixed from previous versions
  • Fixed problem with IMAGEFILENAME functional attribute
  • Added support for EPSG 26914, 26915, 26917 - 26919
  • Improved handling of Boolean data type
  • Fixed problem when GDatabase could not be instantiated via .NET Activator
  • Fixed problem with select set properties from buffer zone
  • Fixed issue with table names on 64bit systems
  • Added support for Polish coordinate systems
  • Added support for EPSG 26910
  • Improved handling of NUMERIC and DECIMAL data types
  • Added MS build again and support for compiling with MS VS 2010
  • Fixed another problem with MULTICURVE geometries
  • Fixed problem with deleting tables
  • Fixed problem with Text and Image feature classes not working with PostGIS 2.0
  • Feature classes in Database Utilities alphabetically sorted
  • Fixed problem with MULTICURVE geometries
  • Fixed problem with pick lists
  • Fixed problem with renaming table columns
  • Added support for scandinavian coordinate systems
  • Fixed problem with point geometries
  • Fixed problem with spatial filter
  • Arbitrary database encoding should be supported now (although not tested)
  • Added support for G/I Toolkit
  • Added EPSG 2169
  • Added edit field for specifying the port. The field can be left blank.

Features supported from older versions
  • The table and field names are CASE SENSITIVE now. Moreover, it is possible to use non-ASCII characters (e.g. Cyrillic) in the table and fields names. The names still cannot contain spaces, dots (except schema delimiter), comas, quotes and double quotes.
  • schemas
  • writable views
  • user right handling

Reviews for this release

No reviews yet for this release.