Interesting. That is adding 30% or so to process the trigger. When I do (this
is to a "memory" database):
SQLite version 3.25.0 2018-06-11 01:30:03
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite>
I have a table where I drop, create and insert 284,000 rows
time taken 3.39 seconds.
I add the following trigger
CREATE TRIGGER x_trigger BEFORE INSERT ON x
WHEN
0 = 1
BEGIN SELECT RAISE ( ABORT, 'raise' );
END;
time taken 4.49 seconds.
And many US ISPs inject extra http request headers containing a
per-customer-tag into HTTP requests so that their bum-buddies can use the
information so provided to more accurately track web usage to a single
customer. This is more prevalent for "Telco" operators, particularly mobile
data
On 10 Jun 2018, at 11:25pm, Keith Medcalf wrote:
> Transport security increases the level of security since it prevents your ISP
> or other malicious poo-heads from tampering with the datastream during
> transport. This is a good thing.
Worth noting that two big ISPs in the United Kingdom
On Sunday, 10 June, 2018 14:27, George wrote:
>I don't feel safer running HTTPS everywhere as Google wants with a
>trust store full of certificates for companies, governments and
>corporations I have never personally met or even trust by name nor
>can I if I so desire disable when I want to.
On 10 Jun 2018, at 9:27pm, George wrote:
> As someone who has not verified the millions of lines of code in SQLite
> I trust the project is taking measure to ensure there stuff does not
> get tampered with, the best way they can, if I remember well that did
> not work even for the Linux kernel a
On Thu, 7 Jun 2018 23:19:22 -0500
"J.B. Nicholson" wrote:
> George wrote:
> > Why can't we have both? I mean the software is in the public domain
> > there is nothing to hide so what's the point of encrypting the site?
>
> ISPs and other intermediaries alter website traffic between the
> server
On Sun, Jun 10, 2018 at 12:45 PM skywind mailing lists <
mailingli...@skywind.eu> wrote:
> Hi,
>
> but to which directory should I set it? There is no general tmp directory
> accessible.
>
> Regards,
> Hartwig
>
> > Am 2018-06-10 um 02:30 schrieb Bob Friesenhahn <
> bfrie...@simple.dallas.tx.us>:
I suggest using a tmp directory within in your private app directory.
- Original Message -
From: skywind mailing lists
To: SQLite mailing list
Sent: Sunday, June 10, 2018, 18:44:45
Subject: [sqlite] Usage of temporary files of SQLite3 on Android / SQLite
commands fail
Hi,
but to
Hi,
but to which directory should I set it? There is no general tmp directory
accessible.
Regards,
Hartwig
> Am 2018-06-10 um 02:30 schrieb Bob Friesenhahn :
>
> On Sat, 9 Jun 2018, skywind mailing lists wrote:
>
>> Hi,
>>
>> currently I am not creating large subqueries or views and
On Sun, Jun 10, 2018 at 7:48 AM Simon Slavin wrote:
> On 10 Jun 2018, at 2:40pm, J Decker wrote:
>
> > forget contributing code ... but funding? how much can I pay to get
> better
> > NUL support?
>
> Can you tell us what's wrong with NUL support ?
>
I have, repeatedly.
> The best changes
On 10 Jun 2018, at 2:40pm, J Decker wrote:
> forget contributing code ... but funding? how much can I pay to get better
> NUL support?
Can you tell us what's wrong with NUL support ?
The best changes come free. Because they're bug-fixes, or obvious improvements
worth the increase in code
On Sat, Jun 9, 2018 at 7:37 PM Andy Goth wrote:
>
> This is probably not going to be added
> until SQLite's primary developers themselves decide they need it, or
> until someone else decides it's important enough to them to contribute
> code and/or funding.
>
forget contributing code ... but
Hi,
I guess there is a typo in the carray documentation:
diff --git a/ext/misc/carray.c b/ext/misc/carray.c
index b39904ae1..32fec3406 100644
--- a/ext/misc/carray.c
+++ b/ext/misc/carray.c
@@ -24,7 +24,7 @@
**
**static int aX[] = { 53, 9, 17, 2231, 4, 99 };
**int i =
> What problem are you having with trigger performance?
My primary use of triggers in SQLite is on insert/update and using RAISE.
Not sure where the trigger overhead comes from, but
If I place a simple check in CHECK and have a trigger with the same CHECK then
CHECK is way faster than a trigger.
15 matches
Mail list logo
