> About Spatial indexes, why not creating them on the fly in memory? If you have large dynamic tables you could instead have a datamodel where min_x, min_y, max_x & max_y indexed columns are added along side the WKT/WKB in the table. Then the QGIS provider could do bbox queries to quickly return the rows within view. Does however have requirement that the application updates these bbox columns.
Question: if you can't use ODBC because of security problems (?) then how are you going to read the MS Access data into QGIS? BTW: QGIS 2.0 has much improved CSV reading support via Text Delimiter reader, including better handling of CR/LF and quotes. Also supports WKT very well and has indexing options. The workflow of MS Access -> query -> export to csv -> QGIS via Add Text Delimited File could still be manageable for users... This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You. _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
