--- Christian Werner <[EMAIL PROTECTED]> wrote:
> Joe Wilson wrote:
> >
> > Hi Christian,
> >
> > Does your ODBC driver allow for SQLite loadable modules out of the box?
> > If so, how do you specify the names of the module DLLs?
>
> No, the extension loading is not supported yet, although compiled into
> the Win32 driver DLLs. But it might be possible to create a SQLite
> function in the SQLite3 driver, which would allow you to write
>
> SQLExecDirect(stmt, "select load_extension('my.dll')", SQL_NTS);
>
> but wouldn't this land us on the shores of hell allowing a new class
> of SQL injection ?
I'm not suggesting something like that.
Nevermind the SQL-injection attack thing, it is not practical to have
a user to run a SELECT statement before they can use their database.
(My Excel SQLite business users would never be able to understand that).
For sqlite extension modules to be useful with minimal effort on the
part of the end-user it should be specified in the ODBC connection
string. i.e.:
DSN=SQLite3 Datasource;Database=my.db;Modules=module1,module2;...
Everyone would know up front what module(s) they would wish to load
for a given ODBC sqlite datasource anyway.
Alternatively, you could put the module name(s) in an .ini file
or in a "special" table within a given sqlite3 database itself.
If this latter approach is chosen it has the power to have
database-specific modules loaded.
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
