<div dir="ltr">regarding how to implement saving SLD in spatialite i downgraded my previous using simple text field... avoiding blob or XmlBlob (SL>4.1)<div><br></div><div>the reason is to allow more simpler interoparability reading back sld. Using directly text I can read it's value directly. values are utf8 enconded and reading them outside qgis context (I received some comments about this) it's simple to understand that text value has a locale coding.</div>
<div><br></div><div>- I decided to avoid sqlite blob because of to simplify interoperability avoiding blob decoding step that it's less uman "natural" </div><div>- I decided to avoid XmlBlob format because it's available only with SL > 4.1. I plan to use this data type when SL 4.1 will be more used. At the moment I preferred to allow this functionality available in all platform and distribution in witch qgis is available and in some of them (e.g. debian wheezy, Ubuntu 13) SL 4.1 it's not packaged.</div>
<div>- I hope to add the same functions to the the new GeoPackage, but this it's not still planned.</div><div><br></div><div>please let me know if there are comments</div><div><br></div><div>code is here:</div><div><a href="https://github.com/luipir/QGIS/tree/spatialite-savestyle">https://github.com/luipir/QGIS/tree/spatialite-savestyle</a><br>
</div><div><br></div><div>diff is here:</div><div><a href="https://github.com/luipir/QGIS/compare/spatialite-savestyle">https://github.com/luipir/QGIS/compare/spatialite-savestyle</a><br></div><div><br></div><div>thank you, </div>
<div><br></div><div>Luigi Pirelli (<a href="mailto:luigi.pirelli@faunalia.it">luigi.pirelli@faunalia.it</a> - <a href="mailto:luipir@gmail.com">luipir@gmail.com</a>)</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 5 February 2014 13:18, Gino Pirelli <span dir="ltr"><<a href="mailto:luipir@gmail.com" target="_blank">luipir@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>I'm developing a new feature to save SLD and ui in Spatialite provider in the same way this function is available for postgres.</div><div><br></div><div>this function developed for Faunalia is funded by ARPA Piemonte<br>
</div><div>fork is available at: <a href="https://github.com/luipir/QGIS/tree/spatialite-savestyle" target="_blank">https://github.com/luipir/QGIS/tree/spatialite-savestyle</a></div><div>and actual modification are localized in this commit: f058bea1fe51116b8231eb5c1ca4faee485c38b2</div>
<div><br></div><div>there are some question about how to develop it and are related how to manage XML in a sqlite/spatialite table.</div><div><br></div><div>this code derive by the postgres provider code where QML and UI xmls are recorded in a XML column. XML is a postgres type. This type is not available in SQlite but it's available in SL 4.1> (called XmlBlob [1])</div>
<div>In this preliminary commit XML is saved in a text column, but saving XML as a blog (blob type in sqlite or XmlBlob in SL) have the advantage to avoid all encoding problems.</div><div><br></div><div>so the question is... sqlite blob or spatialite xmlbob?</div>
<div><br></div><div>Blob type can't allow XML parsing using SQL queries<br></div><div>XmlBlob allows this (using libxml2)</div><div><br></div><div>Blob type is sqlite native type</div><div>XmlBlob can be used only with SL 4.1></div>
<div><br></div><div>My preference is to use native data type Blob. What's you opinion about blob/ xmlblob or whatever</div><div><br></div><div>regards,</div><div><div><div dir="ltr"><br>Luigi Pirelli (<a href="mailto:luigi.pirelli@faunalia.it" target="_blank">luigi.pirelli@faunalia.it</a> - <a href="mailto:luipir@gmail.com" target="_blank">luipir@gmail.com</a>)</div>
</div></div><div><br></div><div>[1] <a href="https://www.gaia-gis.it/fossil/libspatialite/wiki?name=XmlBlob-intro" target="_blank">https://www.gaia-gis.it/fossil/libspatialite/wiki?name=XmlBlob-intro</a></div><div><br></div>
</div></div>
</blockquote></div><br></div></div>