Funny thing! My project is written in PHP! I've just modified pdo_sqlite to get access to the set_authorizer-call! My first solution was much more simple! But hey, you are right!
Regards, Mario 2006/11/14, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
"Mario Wolff" <[EMAIL PROTECTED]> wrote: > Hello Group, > i try to migrate my (alpha-state) project from sqlite2 to sqlite3. To > realize table based acl's i call explain and take the > OpenRead/OpenWrite lines and check for p3 entry which gives the > affected table. With sqlite3 the p3 is not set! > The opcodes in SQLite are not part of the defined interface and are subject to change without notice. Opcodes can and do change sometimes drastically between point releases. Do not write code that reads opcodes. Doing so is considered bad style. To implement table or even column-level access control, use the sqlite3_set_authorizer() API. There are examples of how to do this in the source code to CVSTrac. http://www.cvstrac.org/ -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
