A history of the significant changes in GISquirrel versions.
v1.3.5302 BETA (released 9th July 2021)
- Fixes bug in creation of metadata tables
- Uses latest compatible drivers for PostGIS allowing password authentication with scram-sha-256
v1.3.5071 BETA (released 19th November 2020)
- Compatibility with ArcGIS 10.8
- Resolved exception when opening FeatureClass admin as first GISquirrel dialogue in a session.
v1.3.4698 LTR (released 12th November 2019)
- Resolves error experienced by some users with SQL Server: 'Unable to load DLL "SqlServerSpatial120.dll"'
v1.3.4563 (released 18th October 2019)
- Compatibility with ArcGIS 10.7
v1.3.4529 (released 27th May 2019)
- A few bug fixes
- Improved index maintenance on MSSQL
- Support for PostgreSQL connections to QGISCloud
1.3.4110 BETA (released 23rd May 2018)
- Compatibility with ArcGIS 10.6
1.3.3659 (released 7th January 2017)
- Compatibility with ArcGIS 10.5
- Integrity check can be performed on multiple feature classes.
- Improved spatial index computation and re-computation after editing (from index extent, growing or shrinking).
- Corrected spatial index re-computation for views.
- Improved efficiency of geometry creation from WKB.
1.3.3353 ALPHA (released 8th March 2016)
Compatibility with ArcGIS 10.4.
Ensures PostGreSQL connection dialogue correctly pre-populates all connection properties.
- Handles potential exception on the PostgreSQL connection form that results in the application seeming to stall because the error message pops under an as yet invisible dialogue.
1.3.3174 ALPHA (released 10th September 2015)
Compatibility with ArcGIS 10.3.1.
Type of shapelength/shapearea is checked before inserting values preventing rare type conversion errors when exported GISquirrel feature class is re-imported.
Fixed null exception upon start-up of PostgreSQL connection dialogue.
Corrected logic of the feature class edit dialogue's database schema controls (text vs. combo boxes).
Fixed a bug in the edit layer selection dialogue.
Custom catalogue objects for GISquirrel connection files and datasets enable use of GISquirrel datasets as input of geoprocessing tools and context menu commands of native ArcGIS remote database workspaces.
Added Load data command.
Workspace metadata can now be stored in connection file.
Enabled the "Add GISquirrel ... Workspace" command in ArcMap's "Add Data" dialogue and "Catalog Window" as well as in the ArcCatalog application.
OGC metadata maintenance supports GeoServer metadata table schema.
GISquirrel now properly distinguishes feature classes whose names only differ in casing.
Some metadata queries use PostgreSQL version specific syntax.
Envelope computation no longer fails for feature classes based on views stored in databases whose names contain special characters.
One of the two authentication radio buttons on the SQL Server connection dialogue is always selected.
Edit feature class dialogue no longer defaults to an incorrect schema and as a consequence fails to display a table name in some cases where the underlying table resides outside the default user schema.
Bulk import dialogue no longer erroneously disables the OK button.
Bulk import dialogue no longer falsely reports error adding selected map layers.
Enabled and corrected handling of several PostgreSQL and MSSQL data types.
Enabled editing of PostgreSQL feature classes imported with the "Preserve identifier case" option turned on (i.e. based on tables with mixed-case column names) when the "Preserve identifier case" option is turned off.
When editing a group (multiple feature classes) all edits ares saved in a single transaction.
1.2.2978 BETA (BETA released 27th February 2015)
- Added warning when deleting or editing a DbFeatureClass on which any layers in the current map are based.
- Fixed several issues related to PostgreSQL mixed-case identifiers that could make an imported layer read-only.
- Fixed an issue with column names of re-imported GISquirrel feature classes.
1.2.2949 BETA (BETA released 28th January 2015)
- ArcGIS 10.3 support.
- Exclude features locked by other users when editing started on entire layer.
- GISquirrel feature classes can be used as input into ArcToolbox tools on Windows 8 systems. As always, GISquirrel feature classes must be referenced through map layers in ArcMap; ArcToolbox cannot handle direct references to GISquirrel feature classes in their source workspaces.
- GISquirrel workspaces behave like remote database rather file system workspaces. That is, they are displayed with the remote database icon and the feature classes contained in a workspace are only listed upon connecting to the data source (by double-clicking or clicking the Connect command on the context menu), eliminating a performance bottleneck when feature classes of multiple remote GISquirrel data sources were automatically listed by any catalogue operation in ArcCatalog or ArcMap. Please note that the Connection Properties context menu item still has no effect, as it only operates on native ArcGIS database connection files.
- The Feature Class Admin and Bulk Import dialogues are available in ArcCatalog.
- Feature classes can be renamed and deleted directly in ArcCatalog (i.e without any GISquirrel dialogue). Copy and drag-and-drop operations between workspaces are not supported, however.
- Attribute indexes and their key fields are displayed in ArcCatlog feature class properties dialogue. This is read-only; indexes cannot be added or deleted.
- Corrected a metadata query that for some Microsoft SQL Server Spatial feature classes retrieved incorrect spatial index names.
- Zooming outside current view extent no longer fails to draw geometries when named spatial index of MSSQL feature class doesn't exist.
- Corrected some scenarios in which GISquirrel windows could grow beyond screen size or move off screen.
- NULL values in date fields (date or datetime database columns) properly display as <Null> in the attribute table.
- The incorrect SQL syntax of date queries built by the ArcMap Select by Attributes dialogue is corrected to allow for automatically built queries on the date part.
- Corrected the way potential key columns for feature classes based on MSSQL views are identified.
- Spaces in column names no longer result in invalid SQL statements (parameter names) when importing a layer.
- Saving edits to a table with money or some other numeric column types no longer fails because of an invalid bulk update table creation statemtent.
- Feature class importer now ensures unique key column names.
1.2.2775 BETA (released 7th August 2014)
- Corrected typos in SQL statements that create PostgreSQL domain lookup tables (with thanks to Jeff Maas).
- Lookup tables names now follow the same rules as data tables, including the "Preserve identifier case" setting.
- PostGIS envelope computation makes just one rather than repeated attempts to create missing table statistics.
- PostgreSQL update statements no longer erroneously use the database default geometry column name but the geometry column name of the table being edited.
- Npgsql array parameters are handled in a way that prevents the latest Npgsql versions from building incorrect SQL statements.
- PostgreSQL :: type casts are removed from default values when creating the default values of the corresponding temporary ArcGIS editing layer.
- PostgreSQL metadata queries ignore deleted columns.
- Fixed an issue with object name casing in MSSQL instances with case sensitive collations.
- MSSQL coded value domain lookup table no longer exceeds data length restrictions on primary key. Domain values and names are truncated to the maximum column size.
- Fixed a problem with the domains metadata table trigger function in PostgreSQL table. The trigger function will be automatically updated in existing databases.
- Fixed bug where computation of layer extent could fail for derived views (i.e. views based on other views).
- Added support for MSSQL database types bit, datetimeoffset, datetime2.
- Resolved inconsistency in handling PreserveIdentifierCase user setting for table names when importing to PostgreSQL.
- Fixed null reference exception when opening feature class administrator window.
- Fixed a bug that prevented a GISquirrel layer from being added to a map through an API call.
- Improved computation of extent of layers based on views.
- Added binaries for ArcGIS 10.2.1 and 10.2.2
- Added the ability to rename, delete and copy GISquirrel feature classes in ArcCatalog. Copying and pasting can only be implemented between GISquirrel workspaces; it is not possible to paste a GISquirrel feature class into a non-GISquirrel workspace or a non-GISquirrel feature class into a GISquirrel workspace.
- "Computed columns" (not in the technical sense) such as window functions (e.g. row_number) may now be accepted as primary keys of layers based on views. It is the user's responsibility to make sure that these columns contain unique non-null values. This behaviour is controlled by a user configuration setting that is off by default and may be enabled through the Options dialogue.
- GISquirrel windows are now automatically re-centred when they don't fit in the screen workarea.
- Resolved issue where SQL Server Spatial library could fail to load on some systems.
- Layers based on views that aren't updatable can be made editable by adding INSTEAD OF triggers (in PostgreSQL also unconditional INSTEAD OF rules).
- Fixed bug where the Feature Class Administrator failed to open when last used connection file pointed to an inaccessible database.
- Fixed bug where Import to PostgreSQL could fail for certain feature classes with mixed case column names.
- Trigger on domains metadata table is now expressly created in same schema as the domains table itself. Thanks to Jerry Workman for discovering and diagnosing this issue.
- When importing a GISquirrel feature class to a different database platform, default values that are function calls are no longer added to the output table.
- Fixed bug where Feature Class Import dialogue could raise an error when switching to a PostgreSQL database.
1.2.2453 (released 23rd September 2013)
- Compatible with ArcGIS 10.2
1.2.2433 (released 30th August 2013)
- Enabled automatic maintenance of OGC metadata tables for GISquirrel layers (optional).
- Added "Options" dialogue to main GISquirrel menu, to control this OGC maintenance and other options explained here.
- Fixed bug where an error was raised on saving edits with tables not containing the optional "asq_lockedby" field.
- Improved resilience in multi-user editing when multiple users share the same database login.
- Improved automatic detection of primary key fields to include dynamically generated identifiers (e.g. created with row_number() OVER ...).
- Improved positioning and sizing of the Feature Class Administrator window when large number of feature classes are present.
- Improved feedback when problems occur during layer imports; previously the diagnostic messages were not visible at the end of the process.
1.2.2293 (released 3rd May 2013)
- During imports of new layers the spatial index is now created after the records have been imported instead of before, significantly speeding up the import process and avoiding index fragmentation.
- "INSTEAD OF UPDATE/INSERT/DELETE" triggers/rules are now taken into consideration when determining whether or not views are editable. Full details of the new behaviours are described here.
- Minor bug fixes in bulk importer validation.
- New context menu command on the bulk import form: toggle “Add to map” switch for all imported layers.
- Bulk import now raises a message when all layers have been imported or an error is encountered.
- Fixed a layout issue on the feature class administrator dialogue whose feature class grid could grow to cover up the button when a large number of feature class was present in a database.
1.2.1 (released 4th March 2013)
- Minor bug fixes over 1.2.0
1.2.0 (released 25th February 2013)
- Product name changed to GISquirrel
- Added support for PostGIS databases
- Added Bulk Import function
- Improved speed and efficiency of saving edits
- Fixed issue where importing a layer with a single point feature could fail
- Feature class admin now allows adding multiple layers to the map at once (multi-select using Shift/Ctrl in grid).
- Feature class admin uses familiar ArcMap layer ordering logic when adding layers to the map, and adds new layers into a group if the group is pre-selected.
- Withdrew official support for GISquirrel with SQL Server 2000 and 2005.
1.1.0 (released 1st November 2012)
- Compatible with ArcGIS version 10.1
- Added coordinate system browser
1.0.20 (released 11th November 2010)
- Compatible with ArcGIS 10
- Fixed issue where layers would not draw if the regional decimal symbol was set to ","
1.0.19 (released 25th June 2010)
- Added Developer API
- Fixed issue where layers based on views could fail with mixed collations
1.0.18 (released 30th January 2010)