Add ability to set an int64 file control

[jonstacks]

Similar to #1000,

We are using vfs=memdb and would like to use the SQLITE_FCNTL_SIZE_LIMIT opcode with sqlite3_file_control:

The SQLITE_FCNTL_SIZE_LIMIT opcode is used by in-memory VFS that implements sqlite3_deserialize() to set an upper bound on the size of the in-memory database. The argument is a pointer to a sqlite3_int64. If the integer pointed to is negative, then it is filled in with the current limit. Otherwise the limit is set to the larger of the value of the integer pointed to and the current database size. The integer pointed to is set to the new limit.

Calling the existing SetFileControlInt method when go decides that ints are int64 based on your architecture seem to overflow the C.int and in our case set the size limit of our in-memory VFS to 0. This adds a new SetFileControlInt64 to be used with op codes that expect a sqlite3_int64.

[rittneje]

Calling the existing SetFileControlInt method when go decides that ints are int64 based on your architecture seem to overflow the C.int and in our case set the size limit of our in-memory VFS to 0.

I filed #1299 for this bug.

[jonstacks]

CIFuzz failure was caused by #1300. I'll rebase this and hopefully that fixes the issue 🤞