How about hitting your injection problem from the other side? Perhaps you
can validate the data that is going in to making up your query.
I don't know what query in particular you are using, but it made me think
and something that cannot work with parameterisation could be something like
the
See http://sqlite.mobigroup.ru/src/wiki?name=WClark
To use READONLY, it should form part of a constraint clause for the
column. So, for example:
CREATE TABLE t (i integer readonly); or CREATE TABLE t (i integer
constraint my_constraint readonly);
READONLY stops the value being modified through
daniel.hagl...@trafikverket.se wrote:
> There seems to be lots of information in the mailing list regarding read-only
> databases and locking when it comes to databases on
> disk. Both locking and read-only mode seems to be functionality requiring a
> file on disk. Is it even possible to have
There seems to be lots of information in the mailing list regarding read-only
databases and locking when it comes to databases on disk. Both locking and
read-only mode seems to be functionality requiring a file on disk. Is it even
possible to have locking or read-only mode with in-memory
4 matches
Mail list logo
