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
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
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
>
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
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
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
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
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
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
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
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
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,
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
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".
14 matches
Mail list logo
