Hello, In certain cases when I try to create a virtual table, sqlite3_declare_vtab() returns SQLITE_MISUSE. Nothing appears to be wrong with the string I pass to the sqlite3_declare_vtab(). That is, if I execute the "create table" statement in that string, a regular table will be created - no error.
Is there a way to get more hints why sqlite3_declare_vtab() fails? The only thing special when it fails is that xCreate, before the call to sqlite3_declare_vtab, has (successfully) run and finished statements (prepare/step/finalize) which involve a virtual table using the very same module. Is it forbidden to nest virtual tables this way? That is, having xCreate trigger a call to itself (using different arguments). I'm pretty sure that I don't use non-const static variables which could mess up things. Perhaps sqlite3 does? -- Steinar _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
