I've created a module which will take a table as an argument. In Xconnect it will run a query on that table. Then I accidently used the name of the virtual table in the argument list:
CREATE VIRTUAL TABLE v USING my_module(v); which seems to have triggered an infinite call loop. I suppose what's going on is that when Xconnect tries to run a query on that table, SQLite will try to create the virtual table again, and then loops and quickly overflows the stack. Is this a SQLite bug, or should the virtual table code somehow detect that the user is trying to create a virtual table using itself? Or should the user be blamed? I suspect that this kind of loop could be less obvious if several virtual tables are involved in a loop. In my opinion the cleanest approach would be that SQLite itself determines that it has nested too deeply and gives an error. This is version 3.7.10. -- Steinar _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
