Very interesting indeed! ls ~/Library/Caches/Homebrew/sqlite-* sqlite-3.7.10.tar.gz sqlite-3.7.13.tar.gz
# # in original (failing) terminal # sqlite3 --version 3.7.7 2011-06-25 16:35:41 8f8b373eed7052e6e93c1805fc1effcf1db09366 which sqlite3 /usr/bin/sqlite3 # # in new (succeeding) terminal # which sqlite3 /usr/local/bin/sqlite3 It appears that the original version of sqlite3 that shipped with OS X is still in the PATH of the old terminal, but the new one installed with brew in loaded in the new on. Thanks for helping me figure this out! AJ ONeal On Sat, Jul 21, 2012 at 1:11 AM, Dan Kennedy <danielk1...@gmail.com> wrote: > On 07/21/2012 02:03 PM, AJ ONeal wrote: > >> Weird: now that I've reproduced the error (using the script), I can no >> longer reproduce the successful execution: >> >> sqlite3 ':memory:' 'CREATE VIRTUAL TABLE t1 USING fts4(content="", a, b, >> c);' >> >> >> Hmm... yet when I open another terminal window it begins to work again. >> And when I go back to the previous terminal window it fails again. >> >> What about my terminal session / environment might be contributing to this >> behavior? >> > > Using two different SQLite binaries. > > content= is supported by version 3.7.11 or newer (or, unofficially, > 3.7.9 or newer). > > ______________________________**_________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users> > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
