Re: [sqlite] SQLite Authorizer Feature Suggestion

Hi Mihia, Since I am using in-memory database I only have one connection. I don't want the limiting factors to limit all stmt, only some. Regarding pointers used in a remote process. There is no harm if one is aware of the pointer belonging to a remote process. A handle can be anything as long

Re: [sqlite] SQLite Authorizer Feature Suggestion

Alex Katebi wrote: Hi All, For those of us that use SQLite mostly in-memory. Our context is mostly not {sqlite3*} database pointer, it is {sqlite3_stmt*}. Current API? int sqlite3_set_authorizer( sqlite3*, int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), void

[sqlite] SQLite Authorizer Feature Suggestion

Hi All, For those of us that use SQLite mostly in-memory. Our context is mostly not {sqlite3*} database pointer, it is {sqlite3_stmt*}. Current API? int sqlite3_set_authorizer( sqlite3*, int (*xAuth)(void*,int,const char*,const char*,const char*,const char*), void *pUserData ); Can we