-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hamish Allan wrote: > Whether it's > storage-backed or not, won't attempting to create it a second time > always give a "table already exists" error?
Yes. But so what? Your code is already specific to SQLite - ignore the error! > Also, what is the recommended way to build sqlite3 if you want to make > changes to parse.y, given that using the complete source tree tarball > is heavily recommended against (in favour of the amalgamation, which > only contains the generated code)? The amalgamation is effectively 60 or so source files all concatenated together. If you want to change parse.y then you have to use the source tarball since various tools like Lemon need to be built and run. If you do not want to do this as a one off then you are better off doing a checkout from the source control system (Fossil) and having the changes on top of the trunk. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktw3RAACgkQmOOfHg372QRxHQCgvcuWLsFb2ukf4mQQBnD3B4kP 41kAoLjBiCvv2Z6IApznnBCD0aafahTn =P3cr -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
