Re: [sqlite] Issue with sqlite3_uri_parameter

Actually, SQLite does use sqlite3_uri_parameter indirectly via sqlite3_uri_boolean, but I haven't been able to blow up sqlite3 by supplying malformed URIs.  I thing sqlite3ParseUri throws bad options away. On Thursday, July 3, 2014 3:20 PM, Peter Aronson wrote: > > >I

Re: [sqlite] Issue with sqlite3_uri_parameter

I believe the function expects URIs of the general form (before separators are converted to Nuls) of file:filename?param1=value1=v2 coverted into file nul param1 nul value1 ... which means that the argument to this function is always expected to have an odd number of strings.  Your input has an

[sqlite] Issue with sqlite3_uri_parameter

Hello, Using VFS and sqlite3_uri_parameter, it appears that it ends with an Access Violation. Looking a bit more closely to the code of this function: SQLITE_API const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam){ if( zFilename==0 ) return 0; zFilename +=