Back to <a Wiki page</a><hr><br>
<h1>Changes introduced starting since version 1.8.0</h1>
<h2>1 - Executing more SQL statements in a single shot</h2>
<img alt="multiple SQL statements"><br>
The execution of multiple SQL statements in a single pass is now supported:
<ul>
<li>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.</li>
<li>only the (if any) returned by the most recent SQL statement being successfully executed will be shown in the panel.</li>
<li>explicitly terminating each single SQL statement by inserting a (<b>;</b>) is an always suggested good practice when executing multiple statements.</li>
</ul><br>
<hr>
<h2>2 - DB connections and Security modes</h2>
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.<br>
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.<br><br>
The standard approach implemented by is the one to always keep completely disabled all these potentially harmful SQL functions, unless the <u><i>environment is explicitly set by the user.<br>
Now <b>spatialite_gui</b> support a smarter and easiest approach, completely based on internal actions and no longer requiring any explicit user action.<br><br>
<img alt="not connected"><br>
<u>Please note</u>: now a small always shows the status of the current DB Connection.
<h3>case A) connecting to a sane DB</h3>
<img alt="security relaxed"><br>
<b>spatialite_gui</b> will now always perform a preliminary sanity check <b>before</b> connecting any already existing DB.
<ul>
<li>if no actual threat is found, then <b>spatialite_gui</b> will automatically enable
<li>thus allowing the user to freely invoke all security-related SQL functions without any restriction.</li>
<li>in this case the <u><i>connection will be the one shown in this figure.</li>
</ul>
<h3>case B) starting a READ ONLY DB connection</h3>
<img alt="security read only"><br>
<ul>
<li>anyway whenever a <b>READ ONLY</b> connection is established the ordinary security restrictions will always be enforced.</li>
<li>in this case the <u><i>connection will be the one shown in this figure.</li>
</ul>
<h3>case C) connecting to a potentially harmful DB</h3>
<img alt="security alert"><br>
In the unlucky case that the preliminary security check would identify some problematic Trigger, an appropriate <u><i>security will be immediately raised.<br><br>
<img alt="security lock"><br>
<ul>
<li>in this case the ordinary security restrictions will always be enforced.</li>
<li>the <u><i>connection will be the one shown in this figure.</li>
<li><u>Please note well</u>: anyway an external (i.e. from the command shell) declaration will still continue to be honored.</li>
</ul>
<h2>3 - RasterLite2 integrated support</h2>
Starting since version <b>1.8.0</b> <i>librasterlite2</i> becomes integral part of <b>spatialite_gui</b> (i.e. it will become a not configurable mandatory dependency).
<h3>3.1 - Raster Coverages</h3>
<img alt="raster coverages 1"><br>
All RasterCoverage-related tables will be hierarchically grouped on a distinct branch of the Tables Tree.<br><br>
<img alt="raster coverages 2"><br>
Administering all <u><i>SLD/SE for each single Raster Coverage will now be directly accessible via the corresponding context menu.
<h3>3.2 - SLD/SE Styles administration</h3>
<img alt="raster styles 1"><br>
<ul>
<li>this <u><i>dialog will report all SLD/SE Styles defined for each single Raster Coverage.</li>
<li>and the same dialog could be used in order to add (or even remove) SLD/SE Styles.</li>
</ul>
<br>
<img alt="raster styles 2"><br>
<u>Please note</u>: when importing external SLD/SE Styles selecting more files in a single pass is a supported option.
<h3>3.3 - Coverage Tiles Preview</h3>
<img alt="tile preview 1"><br>
For each table (the one effectively containing raster tiles) a <b>preview</b> feature is supported.<br><br>
<img alt="tile preview 2"><br>
Each tile will be shown accordingly to the Coverage's style.<br><br>
<img alt="tile preview 3"><br>
In the special case of tiles adopting some exotic pixel format (e.g. UINT32, FLOAT or DOUBLE) a default rendering will be adopted.<br>
In the very special case of pixels only the first band (<b>Band #0</b>) will be shown.
<br><br><hr>
Back to <a Wiki page</a>