Updated SQLite bindings to support SQLITE_ENABLE_UPDATE_DELETE_LIMIT flag

[elgris]

Supports #213.

Please consider this PR as a major change because it updates SQLite bindings to version 3.8.10.2.
The amalgamation source code was built with SQLITE_ENABLE_UPDATE_DELETE_LIMIT flag enabled.

[mattn]

Please don't upgrade sqlite3.c. go has problem about this.

golang/go#9356

[elgris]

Hm... Is it because of version 3.8.10.2 or there is another reason and current squirrel-binding.c is highly customized?Is it ok to rebuild sqlite.c v3.8.5 (as it is in master right now), but with SQLITE_ENABLE_UPDATE_DELETE_LIMIT enabled?

[mattn]

Yes, please.

[elgris]

Ok, I rolled back bindings to v3.8.5. Could you please check failing scenario on Windows?

[mattn]

Hmm, totally diff seems deleted/appended into sqlite3-binding.c. I'm thinking we can't touch sqlite3-binding.c for now.

[elgris]

Actually, this is rebuilt version of sqlite3-binding.c. I built it from the sources of version 3.8.5 (like it was before), just added SQLITE_ENABLE_UPDATE_DELETE_LIMIT flag at configure and build steps. Generally, this is the same code, just with extra function added

[ghost]

@mattn any word on this? I could really use it.

[mattn]

https://www.sqlite.org/compile.html

If this option is defined, then it must also be defined when using the 'lemon' tool to generate a parse.c file. Because of this, this option may only be used when the library is built from source, not from the amalgamation or from the collection of pre-packaged C files provided for non-Unix like platforms on the website.

Is this your expected?

[ghost]

@mattn yes

[mattn]

Could you please rebase master?

[gjrtimmer]

Should be closed because of #564

[mattn]

note that not mean that this enabling delete limit also when using libsqlite3 on system always.