IIRC there's a GNOME interface to databases, libgda, that works this way. The fundamental problem with using SQLite3 virtual tables to access remote/high-latency resources is that the SQLite3 VM and the generated bytecode are very serial, therefore the VM can't make progress on other parts of a query while waiting for a virtual table operation to complete.
In principle nothing stops one from adding support for using co-routines in the VM to better exploit concurrency in a query whose plan could evince concurrency. But that doesn't exist yet in SQLite3. IMO this would be a very good thing to add to SQLite3, and it would make it a great meta-DB. But I'm not sure that the SQLite3 developers would welcome it. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users