[sqlite] PhoneGap with SQLite Encryption Extension?
We have an Android application built on PhoneGap, which uses the built-in SQLite to store data. Does anybody here know if it's possible to replace the built-in SQLite in PhoneGap (Android) with a version that supports encryption (S.E.E. or other kind), so that the application information would be transparently encrypted? Thanks, glauber
[sqlite] website documentation wording
On 04 Dec 2015 at 17:13, Simon Slavin wrote: > The worst one is the collective corporation. Is it "Intel has decided" or > "Intel have decided" ? Whichever one I write for whichever side of the > Atlantic, I get told off for getting it wrong. I go with the US version in this instance; Intel is a corporation. WRT SQL pronunciation: no-one here says "sequel", not me, not SWMBO, nor, AFAICT, the cat, although he hasn't actually ventured an opinion. There's a bloke tomorrow I could ask - he's selling us a pendulum wall clock with Westminster chimes. -- Cheers -- Tim
[sqlite] PhoneGap with SQLite Encryption Extension?
On 12/4/15, Ribeiro, Glauber wrote: > We have an Android application built on PhoneGap, which uses the built-in > SQLite to store data. > > Does anybody here know if it's possible to replace the built-in SQLite in > PhoneGap (Android) with a version that supports encryption (S.E.E. or other > kind), so that the application information would be transparently > encrypted? > You'll have to compile in your own copy of SQLite using the JNI. Instructions here: http://www.sqlite.org/android/doc/trunk/www/index.wiki -- D. Richard Hipp drh at sqlite.org
[sqlite] vtfunc wrapper for Python
Hi, I just wanted to share a new tool I wrote that makes it very easy to
write table-valued functions with Python. Basically this is a wrapper
around a virtual table, allowing the Python developer to write two methods
(initialize and iterate) and get the full table-valued function benefits.
The way it works is your Python implementation defines a list of columns
(return values) and params (hidden columns). When the function is invoked
via SQLite, the param values are passed in to the Python initialize method.
Here is how the "generate series" implementation looks:
from vtfunc import TableFunction
class GenerateSeries(TableFunction):
params = ['start', 'stop', 'step']
columns = ['output']
name = 'series'
def initialize(self, start=0, stop=None, step=1):
self.start = start
self.stop = stop or float('inf')
self.step = step
self.curr = self.start
def iterate(self, idx):
if self.curr > self.stop:
raise StopIteration
ret = self.curr
self.curr += self.step
return (ret,)
If you're interested, the source code is up on github:
https://github.com/coleifer/sqlite-vtfunc
I've also written a blog post:
http://charlesleifer.com/blog/sqlite-table-valued-functions-with-python/
Lastly, I wonder if the SQLite development team would be amenable to the
idea of creating a standard API for creating table-valued functions,
something along the lines of the one used in this Python project? Basically
a wrapper around the current virtual table interface.
Thanks for reading! Any feedback would be most welcome,
Charlie
[sqlite] website documentation wording
On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: > It is actually in the ISO standard that the proper pronunciation is ?ess cue > ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. Unfortunately I work as a contractor and if I can pick up the client's pronunciation and copy it, the client likes me more. So I flip back and forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and lots of other computer-related terms, depends on who's paying me that month. The worst one is the collective corporation. Is it "Intel has decided" or "Intel have decided" ? Whichever one I write for whichever side of the Atlantic, I get told off for getting it wrong. Simon.
[sqlite] website documentation wording
Agreed, almost everyone around here says "sequel", too.
On Fri, Dec 4, 2015 at 1:53 PM, Don V Nielsen wrote:
> Tangeant off this note, kind of a history question. "an SQLite". I
> personally would write "a SQL" because it is "sequel" to me. When did
> SQL--sequel become SQL--ess queue ell? I always remember it as being
> sequel, and it rolls off the tongue easier. And as sequel, it would be "a
> SQLite".
>
> Happy Holidays, all.
> dvn
>
> On Thu, Dec 3, 2015 at 3:41 PM, Bernardo Sulzbach gmail.com
>> wrote:
>
>> Good catch, Dirk
>>
>> On Thu, Dec 3, 2015 at 4:47 PM, Dirk Jagdmann wrote:
>> > I'm currently looking at https://www.sqlite.org/autoinc.html
>> >
>> > I suggest you change "You can access the ROWID of an SQLite table using
>> > one {of} the special column names..." and insert the word "of".
>> >
>> > --
>> > ---> Dirk Jagdmann
>> > > http://cubic.org/~doj
>> > -> http://llg.cubic.org
>> > ___
>> > sqlite-users mailing list
>> > sqlite-users at mailinglists.sqlite.org
>> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>>
>>
>> --
>> Bernardo Sulzbach
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
--
Bernardo Sulzbach
[sqlite] website documentation wording
I?d rather be a dinosaur with a clue, then buzzword compliant whipper-snapper. The amusing thing is if you?re really been doing databases since the early 1970s, you likely do call it ?sequel,? since that is what IBM actually called the first relational database language (SEQUEL - Structured English QUEry Language), but it was changed to SQL right before launch due to trademark issues. My guess is, at the time, "ess-cue-ell,? was preferred since there was a need to differentiate it from the existing trademark. -j, who had Eggplant Normal Form (baked) for lunch today On Dec 4, 2015, at 12:08 PM, Keith Medcalf wrote: > > Well, a Gartner Report paid for by Microsoft, which said that if you > pronounced it "ess queue ell" you were labelling yourself as a professional > programmer who understood relational database technologies, had probably used > them since the 1970's or before, and belonged in a dinosaur pen. > > On the other hand, the modern "buzzword compliant" pronunciation for "mere > coders" that had no knowledge of how relational database systems worked and > could not distinguish Boyce-Codd Normal Form from an Eggplant was "sequel". > >> It is actually in the ISO standard that the proper pronunciation is "ess >> cue ell". It became "sequel" in some circles, mostly thanks to Microsoft. >> >> The "Using SQLite" O'Reilly book also uses "an" (e.g. "an SQL statement") >> for the same reasons. >> >> -j >> >> >> On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: >> >>> Tangeant off this note, kind of a history question. "an SQLite". I >>> personally would write "a SQL" because it is "sequel" to me. When did >>> SQL--sequel become SQL--ess queue ell? I always remember it as being >>> sequel, and it rolls off the tongue easier. And as sequel, it would be >> "a >>> SQLite". >>> >>> Happy Holidays, all. >>> dvn >>> >> >> -- >> Jay A. Kreibich < J A Y @ K R E I B I.C H > >> >> "Intelligence is like underwear: it is important that you have it, but >> showing it to the wrong people has the tendency to make them feel >> uncomfortable." -- Angela Johnson >> >> >> >> >> >> ___ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
[sqlite] website documentation wording
Intel is a Corporation. Intel cannot, as a matter of fact and law, anywhere on the planet, decide anything. On the other hand, Intel's Management can make decisions. Therefore the correct statements are: Intel's Management has decided -- for the imperfect tense. Intel's Managemant have decided -- for the past perfect tense. To imply that a corporation has a power to do something which it cannot is simply sloppy writing. > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Tim Streater > Sent: Friday, 4 December, 2015 11:40 > To: SQLite mailing list > Subject: Re: [sqlite] website documentation wording > > On 04 Dec 2015 at 17:13, Simon Slavin wrote: > > > The worst one is the collective corporation. Is it "Intel has decided" > or > > "Intel have decided" ? Whichever one I write for whichever side of the > > Atlantic, I get told off for getting it wrong. > > I go with the US version in this instance; Intel is a corporation. > > WRT SQL pronunciation: no-one here says "sequel", not me, not SWMBO, nor, > AFAICT, the cat, although he hasn't actually ventured an opinion. There's > a bloke tomorrow I could ask - he's selling us a pendulum wall clock with > Westminster chimes. > > -- > Cheers -- Tim
[sqlite] SQLite - Support for VSS writer
On 3 December 2015 at 22:00, Richard Hipp wrote:
> On 12/3/15, Murdare, Vijaykumar S (GE Oil & Gas)
> wrote:
> > Hi,
> >
> > Also, I would like to know while taking the backup of online databases:
> >
> > 1) If read operation is in progress, then can I take backup safely
> with
> > file copy or any other third party tool?
>
> Yes.
>
It's not directly relevant to this Windows thread, but this approach
requires caution on unix platforms if the file copy is done in the same
address space as sqlite3. As noted in
https://www.sqlite.org/howtocorrupt.html (section 2.2), closing a file
descriptor in POSIX land discards all locks associated with that
descriptor's file path, regardless of whether that fd was used to acquire
the lock.
Some [terrible] code to illustrate the approach I'm talking about:
char buf[4096];
int src, dest, n;
sqlite3 *db;
sqlite3_open("db.sqlite", );
// obtain read lock
sqlite3_exec(db, "BEGIN; SELECT COUNT(*) FROM sqlite_master;", NULL,
NULL, NULL);
src = open("db.sqlite", O_RDONLY);
dest = open("db.sqlite.bak", O_WRONLY);
while ((n=read(src, buf, sizeof(buf))) > 0) {
write(dest, buf + i, n - i); // XXX ignores errors/interrupted
syscalls
}
close(dest);
// despite the fact that sqlite3 has a completely separate file
descriptor for
// the database, closing our FD here drops sqlite3's locks!!
close(src);
sqlite3_exec(db, "COMMIT;", NULL, NULL, NULL);
sqlite3_close(db);
Note the comment on close(src) - this approach drops sqlite's locks
*before* the transaction finishes. If you only have a read lock and don't
use the database connection after the close this is probably safe, but if
you have a write lock (either as part of the current transaction or via a
different database connection in some other thread) it is definitely not
safe.
When you start fiddling with the database behing sqlite's back, you need to
be careful!
-Rowan
[sqlite] website documentation wording
I much prefer S Q L to SEQUEL, but that annoyance is nothing compare to saying "SPROC" vs "stored procedure". Not sure quite *why* that bothers me so, but it does. Or rather did: My current job isn't in a predominantly database driven environment so I haven't had to listen to a lot of SQL lingo for 4.5 years or so. :) On Fri, Dec 4, 2015 at 11:10 AM, Scott Doctor wrote: > > Simply "Intel decided". using 'have', 'has', 'has been', 'have been' can > almost always be dropped entirely or replaced with 'is', 'was', 'were' > depending on tense. > > > Scott Doctor > scott at scottdoctor.com > -- > > > On 12/4/2015 9:13 AM, Simon Slavin wrote: > >> On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: >> >> It is actually in the ISO standard that the proper pronunciation is ?ess >>> cue ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. >>> >> Unfortunately I work as a contractor and if I can pick up the client's >> pronunciation and copy it, the client likes me more. So I flip back and >> forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and >> lots of other computer-related terms, depends on who's paying me that month. >> >> The worst one is the collective corporation. Is it "Intel has decided" >> or "Intel have decided" ? Whichever one I write for whichever side of the >> Atlantic, I get told off for getting it wrong. >> >> Simon. >> ___ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> >> >> > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison
[sqlite] website documentation wording
Well, a Gartner Report paid for by Microsoft, which said that if you pronounced it "ess queue ell" you were labelling yourself as a professional programmer who understood relational database technologies, had probably used them since the 1970's or before, and belonged in a dinosaur pen. On the other hand, the modern "buzzword compliant" pronunciation for "mere coders" that had no knowledge of how relational database systems worked and could not distinguish Boyce-Codd Normal Form from an Eggplant was "sequel". > It is actually in the ISO standard that the proper pronunciation is "ess > cue ell". It became "sequel" in some circles, mostly thanks to Microsoft. > > The "Using SQLite" O'Reilly book also uses "an" (e.g. "an SQL statement") > for the same reasons. > > -j > > > On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: > > > Tangeant off this note, kind of a history question. "an SQLite". I > > personally would write "a SQL" because it is "sequel" to me. When did > > SQL--sequel become SQL--ess queue ell? I always remember it as being > > sequel, and it rolls off the tongue easier. And as sequel, it would be > "a > > SQLite". > > > > Happy Holidays, all. > > dvn > > > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Intelligence is like underwear: it is important that you have it, but > showing it to the wrong people has the tendency to make them feel > uncomfortable." -- Angela Johnson > > > > > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] website documentation wording
Simply "Intel decided". using 'have', 'has', 'has been', 'have been' can almost always be dropped entirely or replaced with 'is', 'was', 'were' depending on tense. Scott Doctor scott at scottdoctor.com -- On 12/4/2015 9:13 AM, Simon Slavin wrote: > On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: > >> It is actually in the ISO standard that the proper pronunciation is ?ess cue >> ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. > Unfortunately I work as a contractor and if I can pick up the client's > pronunciation and copy it, the client likes me more. So I flip back and > forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and lots > of other computer-related terms, depends on who's paying me that month. > > The worst one is the collective corporation. Is it "Intel has decided" or > "Intel have decided" ? Whichever one I write for whichever side of the > Atlantic, I get told off for getting it wrong. > > Simon. > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > >
[sqlite] website documentation wording
It is actually in the ISO standard that the proper pronunciation is ?ess cue ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. The ?Using SQLite? O?Reilly book also uses ?an? (e.g. ?an SQL statement?) for the same reasons. -j On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: > Tangeant off this note, kind of a history question. "an SQLite". I > personally would write "a SQL" because it is "sequel" to me. When did > SQL--sequel become SQL--ess queue ell? I always remember it as being > sequel, and it rolls off the tongue easier. And as sequel, it would be "a > SQLite". > > Happy Holidays, all. > dvn > -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
[sqlite] website documentation wording
Tangeant off this note, kind of a history question. "an SQLite". I
personally would write "a SQL" because it is "sequel" to me. When did
SQL--sequel become SQL--ess queue ell? I always remember it as being
sequel, and it rolls off the tongue easier. And as sequel, it would be "a
SQLite".
Happy Holidays, all.
dvn
On Thu, Dec 3, 2015 at 3:41 PM, Bernardo Sulzbach wrote:
> Good catch, Dirk
>
> On Thu, Dec 3, 2015 at 4:47 PM, Dirk Jagdmann wrote:
> > I'm currently looking at https://www.sqlite.org/autoinc.html
> >
> > I suggest you change "You can access the ROWID of an SQLite table using
> > one {of} the special column names..." and insert the word "of".
> >
> > --
> > ---> Dirk Jagdmann
> > > http://cubic.org/~doj
> > -> http://llg.cubic.org
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>
>
> --
> Bernardo Sulzbach
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
