I would think that you can take any third party encryption routine and use it
to encrypt the entire database.
I would be remiss if I didn't ask how you would store and retrieve the
encryption key, what algorithm you plan to use... All rhetorical questions of
course.
--Original
Hello,
I creates a project with Runtime Revolution. I am using an add-on
(called an external) that comes with RR. I don't have the source for
the external and can't recompile it to include an encryption library.
Does anyone know about a way to encrypt an SQLite database without
having to
On Sat, 24 Jul 2010 18:50:05 +0200, Kees Nuyt
wrote:
>There's also pdo_sqlite_external which uses the sqlite3.dll
>the user provides, so you can use the latest and greatest
>sqlite version without having to wait for incorporation in
>PHP or PDO itself.
Thanks guys for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2010 05:38 AM, ve3meo wrote:
> I am a humble user of the command line implementation and of various SQLite
> managers and not an application developer so I cannot do it in code.
You are coding! The command line tool is merely a thin
On Sat, 24 Jul 2010 09:18:57 -0400, "J. King"
wrote:
> PDO_sqlite3 also does have the advantage of being available by default
> since PHP 5.0.0, whereas sqlite3 is only available by default since PHP
> 5.3.0. I'm aware of no other advantages to using PDO, and from what
On Sat, 24 Jul 2010 08:38:31 -0400, "ve3meo"
wrote:
>"Roger Binns" wrote in
>message news:4c4a5bd5.5010...@rogerbinns.com...
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 07/23/2010 07:47 PM, ve3meo wrote:
>>> Is it possible to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2010 04:42 AM, Tim Romano wrote:
> Quite a few users of SQLite these days are not wrapping
> the SQLite libraries in their own client app but are communicating with the
> database via a bridge as if it were a remote server engine.
Yes, but
On 24/07/10 15:41, Alan Chandler wrote:
> On 24/07/10 14:18, J. King wrote:
>
>> PDO_sqlite3 also does have the advantage of being available by default
>> since PHP 5.0.0, whereas sqlite3 is only available by default since PHP
>> 5.3.0. I'm aware of no other advantages to using PDO, and from what
On 24/07/10 14:18, J. King wrote:
> PDO_sqlite3 also does have the advantage of being available by default
> since PHP 5.0.0, whereas sqlite3 is only available by default since PHP
> 5.3.0. I'm aware of no other advantages to using PDO, and from what I've
> read it's on the slow side.
>
Right
Hello,
I created a project with Runtime Revolution. I am using an add-on
(called an external) that comes with RR. I don't have the source for
the external and can't recompile it to include an encryption library.
Does anyone know about a way to encrypt an SQLite database without
having to
On Sat, 24 Jul 2010 08:33:21 -0400, Simon Slavin
wrote:
>
> On 24 Jul 2010, at 9:56am, Gilles Ganault wrote:
>
>> So from the above, it looks like this binary supports access to
>> MySQL(i) and SQLite2/3, in both procedural and (PDO) object-oriented
>> modes.
>>
>> If
"Roger Binns" wrote in
message news:4c4a5bd5.5010...@rogerbinns.com...
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/23/2010 07:47 PM, ve3meo wrote:
>> Is it possible to store the results of a PRAGMA statement, especially
>> PRAGMA
>> database_list in a
On 24 Jul 2010, at 9:56am, Gilles Ganault wrote:
> So from the above, it looks like this binary supports access to
> MySQL(i) and SQLite2/3, in both procedural and (PDO) object-oriented
> modes.
>
> If that's correct, and provided the application doesn't need to be
> DB-agnostic... why should I
Tim,
I, like you, am using SQLite as the DB to a web server. But I have to agree
with Roger. I do so from the prospective that web client cannot make native
calls to SQLite. Thus the web server is the client. Further more I would
say that in all web server based solutions, the web server is
Roger,
It would be more accurate to say that SQL is a library which *can* live
inside an application. Whether it actually does live inside it will depend
on how one is using SQLite. When it is used as a "back-end" reached via
middleware, such as the ADO.NET driver, SQLite does not live inside
Hi all,
I had to recognise that our data-transforming (read: heavily inserting)
procedures had a massive drop in performance with 3.7. Some
investigation showed that this is related to "pager_write_pagelist"
where a hint to an estimated target filesize is given to the filesystem,
which on
I can think of several answers to your last question;
#1 Your mileage may vary
#2 Take the easiest way for you and see it works well.
#3 Since SQL wasn't designed for vector math do it in your program -- probably
MUCH clearer to anybody (including yourself) in the future. It shouldn't take
On Fri, 23 Jul 2010 10:25:13 +0100, Andy Chambers
wrote:
>Hi,
>
>I've been reading about version compatibility between different
>versions of sqlite at the
>link below:
>
>http://www.sqlite.org/formatchng.html
>
>It states the expected behaviour for old and new with a
http://www.sqlite.org/onefile.html
Am 23.07.2010 um 11:25 schrieb Andy Chambers:
> Hi,
>
> I've been reading about version compatibility between different
> versions of sqlite at the
> link below:
>
> http://www.sqlite.org/formatchng.html
>
> It states the expected behaviour for old and new
Hello
I'm using the pre-compiled PHP5-FPM/FastCGI (www.php-fpm.org) which
seem to contain the following DB connectors:
PDO drivers mysql, sqlite, sqlite2
pdo_mysql 5.1.48
pdo_sqlite 3.6.22
SQLite 2.8.17
sqlite3 3.6.22
So from the above, it looks like this binary supports access to
MySQL(i)
20 matches
Mail list logo