"Sarah" <[EMAIL PROTECTED]> wrote: > > I have ported SQLite to an embedded platform. When I debugged on this > platform, I met following problems: > 1. in process_input(), part of codes are like this: > ...... > open_db(p); > rc = sqlite3_exec(p->db, zSql, NULL, p, &zErrMsg); > ...... > it's strange that, after sqlite3_exec executed, it didn't return back to > process_input(), but returned to > the next statement of sqlite3_exec() in function sqlite3InitCallback(). > > What's the possible reason for this?
I do not understand the question. > > 2. What is the consequence of defining SQLITE_OMIT_DISKIO? that is to say, > what the DISKIO do? SQLITE_OMIT_DISKIO disabled the part of SQLite that writes to the disk. This is useful if you want SQLite to use in-memory databases only. Some makers of embedded devices what that. > > 3.When I define #define SQLITE_OMIT_ALTERTABLE and #define > SQLITE_OMIT_TRIGGER in my program, it caused a lot > of compiling and linking errors, most of them comes form parse.o. How to fix > these errors? > You have to rebuild parse.c from parse.y. The makefile will do this for you automatically if your are running Linux. I suggest you do your build on Linux. Or see prior emails on this subject in the mailing list archive. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
