Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Artifact ID:	aac32263b65ae4fc942903280923069b21480032
Page Name:	version-1.8.0
Date:	2014-04-16 20:55:08
Original User:	sandro
Next	4b6bea944aaebb4229a6c43fa4e44f203492b18c

Content

Back to main Wiki page

Changes introduced starting since version 1.8.0

1 - Executing more SQL statements in a single shot

The execution of multiple SQL statements in a single pass is now supported:

execution will immediately stop when some SQL error is eventually found; this practically means that some statements could be effectively processed, while other statements could be ignored due to premature termination.
only the resultset (if any) returned by the most recent SQL statement being successfully executed will be shown in the panel.
explicitly terminating each single SQL statement by inserting a semi-colon (;) is an always suggested good practice when executing multiple statements.

2 - DB connections and Security modes

As you probably remember, there are few SQL functions supported by SpatiaLite that could eventually pose some security concern because they implement some kind of direct data exchange between the DB and the local file-system.
In the worst possible scenario an hypothetical hacker could eventually attempt to attack an external system by offering for download a purposely forged SpatiaLite DB containing maliciously forged Triggers, and the user will then be completely unaware of such a potentially dangerous threat.

The standard approach implemented by libstpatialite is the one to always keep completely disabled all these potentially harmful SQL functions, unless the environment variable SPATIALITE_SECURITY=relaxed is explicitly set by the user.
Now spatialite_gui support a smarter and easiest approach, completely based on internal actions and no longer requiring any explicit user action.

not connected

Please note: now a small icon always shows the status of the current DB Connection.

case A) connecting to a sane DB

spatialite_gui will now always perform a preliminary sanity check before connecting any already existing DB.

if no actual threat is found, then spatialite_gui will automatically enable SPATIALITE_SECURITY=relaxed
thus allowing the user to freely invoke all security-related SQL functions without any restriction.
in this case the connection icon will be the one shown in this figure.

case B) starting a READ ONLY DB connection

anyway whenever a READ ONLY connection is established the ordinary security restrictions will always be enforced.
in this case the connection icon will be the one shown in this figure.

case C) connecting to a potentially harmful DB

In the unlucky case that the preliminary security check would identify some problematic Trigger, an appropriate security alert will be immediately raised.

security lock

in this case the ordinary security restrictions will always be enforced.
the connection icon will be the one shown in this figure.
Please note well: anyway an external (i.e. from the command shell) SPATIALITE_SECURITY=relaxed declaration will still continue to be honored.

3 - RasterLite2 integrated support

Starting since version 1.8.0 librasterlite2 becomes integral part of spatialite_gui (i.e. it will become a not configurable mandatory dependency).

3.1 - Raster Coverages

All RasterCoverage-related tables will be hierarchically grouped on a distinct branch of the Tables Tree.

raster coverages 2

Administering all SLD/SE Styles for each single Raster Coverage will now be directly accessible via the corresponding context menu.

3.2 - SLD/SE Styles administration

this dialog box will report all SLD/SE Styles defined for each single Raster Coverage.
and the same dialog could be used in order to add (or even remove) SLD/SE Styles.

Please note: when importing external SLD/SE Styles selecting more files in a single pass is a supported option.

3.3 - Coverage Tiles Preview

For each <coverage-prefix>_tile_data table (the one effectively containing raster tiles) a preview feature is supported.

tile preview 2

Each tile will be shown accordingly to the Coverage's default style.

tile preview 3

In the special case of tiles adopting some exotic pixel format (e.g. UINT32, FLOAT or DOUBLE) a default grayscale rendering will be adopted.
In the very special case of multi-band pixels only the first band (Band #0) will be shown.

Back to main Wiki page