<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, May 27, 2014 at 7:21 PM, Vincent Picavet <span dir="ltr"><<a href="mailto:vincent.ml@oslandia.com" target="_blank">vincent.ml@oslandia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1eg" class="a3s" style="overflow:hidden">As stated by Regis, basing this work on top of SQLite may be the best option,<br>
but more study has to be done and a general agreement is needed to go this<br>
way.</div></blockquote></div><br>I have plans to implement this. Exposing QGIS layers as SQlite virtual tables. This would give a lot of query bang with low code change  It was done in OGR and works really well, of course it sucks with performance if you do something really complicated but otherwise it would give QGIS a good edge - if you need more power then more to a better database. A basic query-everything type system.  This is something that MapInfo had and is a bit of pain to loose when coming to QGIS. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">I hope to start work after 2.4 is out.</div><div class="gmail_extra"><br></div><div class="gmail_extra">- Nathan</div></div>