You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is easy to pass parameters using URI filename mechanism but it isn't obvious how to receive those parameters in a custom VFS. Document how to do so.
With the current APSW implementation it is impossible to get the URI information. The way it is provided inside SQLite is rather hacky (overloads a char pointer) which makes it even harder to add into APSW without breaking existing code so I'm going to see what I can do for the next release cycle.
Create a URIOptions type. It wraps the incoming char* passed to xOpen and implements sqlite3_uri_parameter(). It is passed to xOpen upcalls (backwards incompatible change). Calls to xOpen can provide either a filename or an URIOptions instance.
From rogerbinns on October 24, 2011 09:47:46
It is easy to pass parameters using URI filename mechanism but it isn't obvious how to receive those parameters in a custom VFS. Document how to do so.
Original issue: http://code.google.com/p/apsw/issues/detail?id=124
The text was updated successfully, but these errors were encountered: