> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> inside of a transaction. OK, that's a bug. I'll fix it. > But in the meantime, your work-around is simple: recompile > with -DNDEBUG=1. That will disable all the asserts. (The > particular assertion failure you are hitting appears to be > completely benign.) This fix, by the way, also has the > nice benefit of making the library run 2x faster. Glad to know it is safe to ignore this one. I'm somewhat of an assert freak and hesitate to turn them off in someone else's code when I am doing something out of the ordinary. That said, manually adding -DNDEBUG=1 to the TCC flags in Makefile did the trick. I don't know if this is of any help to you are not, but as it turns out, this assertion was being triggered right at the end of the process that created the database. When I compared my logs from the failed run and from the NDEBUG run, they were identical except for the assertion. Also the NDEBUG run created a valid SQLite database. The one that asserted produced a corrupted database/journal combination. Thanks a lot. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
