SQLite does not have unsigned integers. All integers are 64-bit signed
entities, but may be stored in shorter integers on disk if the value fits.
This is an internal optimization and not visible externally.
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot
No. GPS time is maintained as WEEKS since the GPS epoch and an offset into the
week (TOW -- time of week). There is an additional field that is the "offset
from UT1" (currently 11 seconds I believe). The receiver uses the information
to calculate UT1. There is, I believe, a flag that says t
create table templog
(
datestamp text collate nocase primary key,
centTemp REAL not null,
fahrTemp REAL
);
create trigger TempLogInsert after insert on templog
begin
update templog set fahrtemp = new.centTemp/9*5+32 where datestamp ==
new.datestamp;
end;
create trigger tempLogUpdate afte
Do you have an appropriate index defined on both the parent and child keys?
.lint fkey-indexes
at a command shell prompt will tell you ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From:
sers-
>[email protected]] On Behalf Of Keith Medcalf
>Sent: Saturday, 9 June, 2018 22:06
>To: SQLite mailing list
>Subject: Re: [sqlite] Idea: defining table-valued functions directly
>in SQL
>
>
>Do you have an appropriate index defined on both the parent and child
&
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. Or
list
>Subject: Re: [sqlite] sqlite.org website is now HTTPS-only
>
>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 duri
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> creat
ta DB (16 columns), the inserts were generated from
>.dump in the shell, about 45MB of input data
>so
>
>BEGIN;
>lots of inserts
>COMMIT;
>
>Run on a laptop i7 with SSD (not that should make any difference to
>the relative performance)
>If I could get your re
t;the overhead? Correct?
>
>On Tue, Jun 12, 2018 at 9:47 AM, David Burgess
>wrote:
>> Specifically, preparation of the "trigger part" of the statement is
>> the overhead? Correct?
>>
>>
>> On Mon, Jun 11, 2018 at 5:16 PM, Keith Medcalf
> wrote:
The tip of trunk also does not parse "Inf" or "-Inf" floating point values (eg:
in an insert statement), but will produce Inf and -Inf output. The bind and
column values interfaces however do handle the IEEE inf/-inf correctly.
Is this a bug/oversight in the parser?
sqlite> create table x(x r
You can replace the "Inf" with 1e400 and -Inf with -1e400. These values will
be parsed and stored as the appropriate plus/minus Infinity since they are
larger than the maximum representable IEEE-754 Double Precision Binary Float.
---
The fact that there's a Highway to Hell but only a Stairway
Exactly.
REAL is the elapsed time according to the wall clock
USER is the actual time the CPU spent executing user code
SYS is the actual time the CPU spent executing system code
In "modern" Operating Systems USER usually reflects CPU usage by your process
while the CPU is in USER mode (non-
Cannot reproduce.
I am using the current trunk that I compile myself with MinGW 8.1.0 on Windows
10 1803 Pro for Workstations. The laptop has a 4 Ghz Quad Core Xeon and the
disk is a Samsung NVMe drive. About the only relevant change is that I have
forced the Windows caching mode from "mag
Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Keith Medcalf
>Sent: Thursday, 14 June, 2018 14:16
>To: SQLite ma
Will it still work if I compile in 64 bit mode?
>
>
>
>
>From: sqlite-users on
>behalf of Keith Medcalf
>Sent: Thursday, June 14, 2018 10:09:50 PM
>To: SQLite mailing list
>Subject: Re: [sqlite] .timer
>
>
>See the following web pa
so, whereabouts?
>
>3 Will it still work if I compile in 64 bit mode?
>
>
>
>
>From: sqlite-users on
>behalf of Keith Medcalf
>Sent: Thursday, June 14, 2018 10:09:50 PM
>To: SQLite mailing list
>Subject: Re: [sqlite] .timer
>
&
It looks for an external sqlite3_win32_utf8_to_unicode function.
Although this is an exported API function the linker on Windows cannot resolve
it at compile time. Even if it could, the loader trampoline could not link it
back to the API in the original (loading) sqlite3 code (especially not i
IN32_FILE_NOBUFFER
>
> dwFlagsAndAttributes |= FILE_FLAG_NO_BUFFERING;
>
>#endif
>
>
>
>Is that correct?
>
>
>
>BTW ‘select * from generate_series(1,10)’ gives me an error ‘no such
>table : generate_series’ in sqlite3.exe. I thought it was compiled
>into t
The increase/decrease in memory is almost certainly the cache (after running
the command once and before flushing look and see what Task Manager says for
"Cached", then look again after you do the flush and see if it releases it.
This is memory that would otherwise be unused being used by the
>You spoon fed me on a previous thread how to load extensions using a
>core_init function placed at the end of the sqlite3.c code. I do have
>the series.c in my core_init so it is available to me and works fine
>in my cpp code. I don’t see how that relates to sqlite3.exe though.
>How do you get ge
You are using Windows 10? It is on the "Performance" tab, select the wee graph
on the right for "Memory". In the detail, right underneath "Available" and
beside "Committed" at the bottom where all the text is. Oh, you have to be in
"more details" view, not in the "simple" default view ...
-
Your other "right", the one on the left :)
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On
Ok, I have been able to reproduce this but have not figured out what is
happening.
And you are correct, it appears to be related to "reading backwards" somehow.
It is unaffected by the WIN32 cache mode that is set (I tested all modes and
they all behave the same -- except that I could not t
management code ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Keith Medcalf
>Sent:
eaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Simon Slavin
>Sent: Friday, 15 June, 2018 17:10
>To: SQLite mailing list
>Subject: Re: [sqlite] .timer
>
>
well.
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-----Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Keith Medcalf
>Sent: Friday, 15 June, 2018
Yeah, I had a lot of problems with the fileio.c extension after the fsdir
virtual table was added. It needs a header file "test_windirent.h" to be
available. I had to do some fiddling to get it to compile properly using MinGW
(GCC) on Windows. I thought Richard had fixed it.
It also makes c
ell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Keith Medcalf
>Sent: Friday, 15 June, 2018 18:28
>To: SQLite mailing list
>Subject: R
ginal Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Keith Medcalf
>Sent: Saturday, 16 June, 2018 11:56
>To: SQLite mailing list
>Subject: Re: [sqlite] .timer
>
>
>I have confirmed that the distributed shell on sqlite.org di
;
>
>
>________
>From: sqlite-users on
>behalf of Keith Medcalf
>Sent: Saturday, June 16, 2018 6:56:19 PM
>To: SQLite mailing list
>Subject: Re: [sqlite] .timer
>
>
>I have confirmed that the distributed shell on sqlite.org displays
>
When you have a temp database in memory it appears that you cannot release the
memory for it. Even after you remove (drop) all the tables in the temp
database, memory usage does not decrease. pragma shrink_memory does not free
the memory and pragma temp.shrink_memory neither. The memory can
No, when you use OFFSET you are reading and discarding rows. There is no
difference between:
select * from t;
and discarding all the results except the last row, and,
select * from t limit ,1;
for a table containing 1 rows. In both cases you have to read the
entire table in
Also note that you probably want your application to store the password as a
salted-hash, and not as a plain-text password. Otherwise someone could look up
the passwords with a text editor ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipat
These are with SQLITE3's memmap turned off (SQLITE_DEFAULT_MMAP_SIZE 0). I set
the MAX_SIZE to 0 as well and it made no difference.
Windows is memmapping the file by itself.
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
The following pure python code does the same thing, memmapping the file when
reading backwards ... works in Python 2 and 3, 32 and 64 bit.
Emulates what sqlite3 is doing as closely as I can manage. As long as the mmap
fits in memory it does not seem to affect performance.
---//---
from __futu
The new "consumer" SSDs from Samsung carry a 1200 TBW/8 year warranty on a 4 TB
device. That is a lot of writing for a "consumer desktop" computer ... that is
about 400 GB written per DAY every day for 8 years!
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
l
0G/day a run
>for
>its money :P
>
>-Rowan
>
>On 19 June 2018 at 12:37, Keith Medcalf wrote:
>
>>
>> The new "consumer" SSDs from Samsung carry a 1200 TBW/8 year
>warranty on a
>> 4 TB device. That is a lot of writing for a "consumer desktop&qu
You know that you can use the hidden columns by name in the WHERE cause
correct, and do not have to use function parameters?
So the ext/misc/series.c in the repository defines a virtual table
generate_series which effectively returns each "value" generated by the
statement:
for (value=start;
Actually, you would probably write:
SELECT aDate
FROM TeachingSaturdaysInSchoolYear
WHERE aDate NOT IN (SELECT aDate
FROM SchoolYearTeachingDays);
Since the subquery is not correlated there is no *need* for aliases ... but if
you want to type more characters you are fr
In the current tip of trunk it pretends the unknown tokens are surrounded by
double-quotes. Until you interpose a non type keyword ... at which point the
parser stops "eating your junk as the type declaration" and resumes the grammar
..
sqlite> create table x(x happy days);
sqlite> pragma tab
If you give the parent column a proper affinity (ie, integer) do you get
"happiness making" results?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>bo
ite.org] On Behalf Of Allen
>Sent: Thursday, 28 June, 2018 10:00
>To: [email protected]
>Subject: Re: [sqlite] sqlite-users Digest, Vol 126, Issue 28
>
>> If you give the parent column a proper affinity (ie, integer) do
>you get "happiness making" results?
>I want a query that returns all of the records with status = 1 and
>unique records, based on name, where the status =0 and the name is
>not in the list status=1
Translation into SQL using English to SQL Translator, using the most direct
translation on the "problem statement" above directly into
pragma application_written_by=coder;
-vs the default, which is-
pragma application_written_by=programmer;
;-)
All of the issues raised are "application" problems, not database problems.
Clearly if you retrieved a value from the database and want to use it as an
index you have to do bounds c
ic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Warren Young
>Sent: Friday, 29 June, 2018 19:35
>To: SQLite mailing list
>Subject: Re: [sqlite] column types and constraints
>
>On Jun 29, 2018, at
You "put" a ieee754 floating point double. If you retrieved an ieee754
floating point double, you would get back that which you put! The fact that
internally SQLite3 stored it as a 3 (integer, token, string, whatever) is
irrelevant. You "gets" what you "puts", as long as what you "putted" is
Re: [sqlite] unique values from a subset of data based on
>two fields
>
>Easier and pretty obvious :) Thanks Keith
>
>
>
>Paul
>www.sandersonforensics.com
>SQLite Forensics Book <https://www.amazon.co.uk/dp/ASIN/1980293074>
>
>On 29 June 2018 at 23:20, Keith Medcal
SQLite will not select the collation based on the index -- it is exactly the
opposite -- the collation requested is used to find an appropriate index.
So if you do an order by that needs BINARY collation, and the only index
available is a NOCASE collation index, that index cannot be used (for
When you declare a column with no affinity (that is with blob or none
affinity), the data is stored precisely and exactly as presented with no
conversions performed by SQLite3. You give it a character string, it stores a
character string. You give it an integer, it stores an integer. You giv
In your case, yes.
If you do not wish SQLite3 to "convert" to the requested storage type on
storage of a value, then do not specify a storage type (or specify a storage
type of BLOB). Then whatever you request-to-store will be stored without
conversion.
SQLite version 3.25.0 2018-06-21 23:53
ginal Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Warren Young
>Sent: Saturday, 30 June, 2018 18:09
>To: SQLite mailing list
>Subject: Re: [sqlite] column types and constraints
>
>On Jun 29, 2018, at 10:17 PM, Keith Medcalf
The "unixepoch" time used by SQLite is an "integer" in whole seconds of
precision. ISO-8601 datetime strings are also "by default" generated in
seconds of precision. If you use strftime rather than datetime then the
ISO8601 strings can be read with "unlimited" precision and written with
mill
You can make a user-defined function on Windows that returns the UnixTime to
the limit of Accuracy of the underlying hardware/software (100 huns max) and to
the limit of precision of the IEEE754 double precision floating point format
with the following (so an accuracy of 100 nanoseconds with a
They are part of the current draft release:
http://www.sqlite.org/draft/releaselog/3_25_0.html
Dan,
I see that there is a new create function to create the window functions which
have some slight changes to the methods being called and what they do.
I presume that a function defined with the
I have overridden the builtin AVG function with a function of my own that
computes the average by using the "running average" method rather than the
simple sum/count method. This function is registered as an old fashioned
aggregate function.
After the window extension is put in place, it appe
sers-
>[email protected]] On Behalf Of Simon Slavin
>Sent: Monday, 2 July, 2018 04:27
>To: SQLite mailing list
>Subject: Re: [sqlite] Window Function Crash -- overriding builtin
>aggregate
>
>On 2 Jul 2018, at 7:40am, Keith Medcalf wrote:
>
>> Even if I reg
gt;From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Dan Kennedy
>Sent: Monday, 2 July, 2018 10:21
>To: [email protected]
>Subject: Re: [sqlite] Window Function Crash -- overriding builtin
>aggregate
>
>On 07/02/201
On Thursday, 5 July, 2018 00:57, Donald Shepherd :
>On Thu, 5 Jul 2018 at 16:45, Simon Slavin >wrote:
>> On 5 Jul 2018, at 7:30am, Clemens Ladisch >wrote:
>>> The expression "x = x" will fail for NULL, but succeed for
>>> everything else. So you can use that to implement a
>>> "not-NULL ELSE"
Correct.
You have stored integer Unix Epoch timestamps. You cannot do "string" searches
on integers (at least not ones like what you have asked for, which involves
conversion of an integer representing a Unix Epoch offset to an ISO-8601
string, not to an ordinary "string representation of t
>SELECT CAST((SELECT (julianday('now', 'localtime') -
>julianday('1970-01-01'))*24*60*60*1000) AS INTEGER);
Are you sure you want to be mixing up timezones?
julianday('1970-01-01') returns the julianday timestamp for 1970-01-01 00:00:00
GMT
julianday('now', 'localtime') returns the julianday t
This will however only work in all GMT/UT1/UTC.
If the "input" (ie, the string) is "localtime" then the localtime modifier
needs to be added to the date() function as in:
date(date_type, 'unixepoch', 'localtime') like '2018-%'
Note that you cannot create an index on the expression date(date_
Why not use MOD (%) as in
ABS(RANDOM() % 6)
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Cecil Wester
-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Cecil Westerhof
>Sent: Sunday, 8 July, 2018 00:59
>To: SQLite mailing list
>Subject: Re: [sqlite] Kind of pivot table
>
>2018-07-08 8:49 GMT+02:00 Keith Medcalf :
>
>>
>> Why not use MOD (%) a
qlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Cecil Westerhof
>Sent: Sunday, 8 July, 2018 02:16
>To: SQLite mailing list
>Subject: Re: [sqlite] Kind of pivot table
>
>2018-07-08 9:10 GMT+02:00 Keith Medcalf :
>
>>
>> sqlite&
.dump in the command line shell?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Randall Smith
>Sent: Mon
sers-
>[email protected]] On Behalf Of Jens Alfke
>Sent: Monday, 9 July, 2018 10:49
>To: SQLite mailing list
>Subject: Re: [sqlite] Kind of pivot table
>
>
>> On Jul 7, 2018, at 11:49 PM, Keith Medcalf
>wrote:
>>
>> Why not use MOD (%) as in
>>
This query will work fine. You could also do something like:
UPDATE tips
SET totalUsed = totalUsed - (SELECT MIN(totalUsed) - 1 FROM tips);
which would include the extra 1 (the new base) in the scalar subquery.
The expression (SELECT MIN(totalUsed) FROM tips) is not correlated with the
out
On Saturday, 14 July, 2018 22:24, Gabriel Chiquini
wrote:
>Hi everyone, I tried to use the normalize function I found on the
>ext/misc folder, but I couldn't load it, it returns the following
>error: "normalize.so: undefined symbol: sqlite3_normalize_init". I am
>using the latest version of sql
Firstly, the SQLITE_DLL define does not exist (is this a bug in the docs>?
Secondly you did not define SQLITE_HAS_CODEC as required to integrate the SEE
codec/
Thirdly a .dll file cannot be created with ar. ar is for creating libraries,
not DLLs. (.a files)
To statically link you should just a
.sqlite.org] On Behalf Of J Decker
>Sent: Friday, 20 July, 2018 12:13
>To: General Discussion of SQLite Database
>Subject: Re: [sqlite] Issue using SEE
>
>On Fri, Jul 20, 2018 at 11:05 AM Keith Medcalf
>wrote:
>
>>
>> Firstly, the SQLITE_DLL define does not exist (
>I have a database with one process (in one thread) writing to it, and
>another process (also in a single thread) reading from it only. All
>writes are done under BEGIN TRANSACTION IMMEDIATE. Sometimes, an END
>TRANSACTION fails with error 5, SQLITE_BUSY. The documentation says
>this should not
>I have a database with one process (in one thread) writing to it, and
>another process (also in a single thread) reading from it only. All
>writes are done under BEGIN TRANSACTION IMMEDIATE. Sometimes, an END
>TRANSACTION fails with error 5, SQLITE_BUSY. The documentation says
>this should not
>In the current use case thre's a single process. The way I see it, in
>the near future it would probably increase to 3-4 processes,
>each doing 10-100 writes per second or so. Each write would be around
>1KB-20KB (one single text field, I guess).
>I wonder if writing data in batches would be help
>> A query doing a single insert of a few bytes with no Indexes, no
>> triggers, no functions will be stupendously fast, whereas any
>> increase in one or more of the above will slow things down.
>> How much exactly is something you need to test, any guesswork
>> will not be useful. What I can
>"SQLITE_ENABLE_LOCKING_STYLE=0","SQLITE_THREADSAFE=0",
>"SQLITE_OMIT_UTF16","SQLITE_ENABLE_COLUMN_METADATA=1",
>"SQLITE_DEFAULT_FOREIGN_KEYS=1"
>Is there something about the combination of options I've used?
Do you get different results when using different options? (of course, if you
turn of
Because the required unique index on copy(id_book, copy_number) exists (in the
table definition).
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun
You observe no violation when VIOLATION is 0 because there is no referential
integrity violation to report ...
However, you are correct that when inserting data the as shown in your code
(where there is a referential integrity violation) the insertion is much slower
after the violation occurs,
sqlite.org] On Behalf Of Dominique Devienne
>Sent: Thursday, 2 August, 2018 01:48
>To: General Discussion of SQLite Database
>Subject: Re: [sqlite] Violated failed foreign key constraint delays
>the rest of transaction ; Some foreign key violations don't trigger
>the error at
key violations don't trigger
>the error at all
>
>On Thu, Aug 2, 2018 at 9:35 AM Keith Medcalf
>wrote:
>
>> You observe no violation when VIOLATION is 0 because there is no
>> referential integrity violation to report ...
>>
>
>Really Keith? Parent IDs are
You misunderstand how dBase databases work. An index is created on a table
(.DBF file) and stored in an index file (.NDX). You can have multiple indexes
associated with a single .DBF file (which means multiple .NDX files). FoxPro
has a non-standard index format that permits the multiple inde
ferential integrity across multiple "attached"
databases, nor use cross "attachment" triggers (but you cannot do that now
anyway).
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message
te-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Jean-Luc Hainaut
>Sent: Thursday, 2 August, 2018 15:04
>To: SQLite mailing list
>Subject: Re: [sqlite] Common index for multiple databases
>
>On 02/08/2018 20:50, Keith Medcalf wrote:
>> In n
Many versions ago a CLI command (that is, the sqlite3 Command Line Interface)
was created so that folks would stop complaining about referential integrity
enforcement being slow when they did not create the indexes that were necessary
to enforce referential integrity (because failing to have th
#x27;s a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: Yuri [mailto:[email protected]]
>Sent: Thursday, 2 August, 2018 16:37
>To: SQLite mailing list; Keith Medcalf
>Subject: Re: [sqlite] Violated failed fore
l but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: Yuri [mailto:[email protected]]
>Sent: Thursday, 2 August, 2018 17:06
>To: SQLite mailing list; Keith Medcalf
>Subject: Re: [sqlite] Violated failed foreign key constraint
Not exactly. The index is stored in the SAME FILE that contains the table.
For example in dBase I (or II or III) you might have the following files:
Customer.DBF
CustNo.NDX
CustName.NDX
where the two NDX files index fields from the Customer.DBF file. In FoxPro you
can have "compound" indexe
On Friday, 3 August, 2018 13:50, Warren Young wrote:
>I’d be careful trying to apply your knowledge directly to SQLite.
>dBase comes out of the non-SQL world, so it’s going to have a
>different outlook in many areas.
>If the following is a fair description of how FoxPro for DOS indexes
>work, th
WITH RECURSIVE
dates(dateD) AS (VALUES(:StartDate)
UNION ALL
SELECT date(dateD, '+1 year')
FROM dates
WHERE date(dateD, '+1 year') <= :EndDate
)
SELECT max(dateD), count(*) FROM dates;
---
The fact that t
On Saturday, 4 August, 2018 20:01, Stephen Chrzanowski
wrote:
>I was right. I got the tables done before a response. But still
>would like to know if there's a SQLite method of doing so.
Of course there is.
>My method was to use a templating application that I wrote at work. I
>give it this
ay to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of Csányi Pál
>Sent: Sunday, 5 August, 2018 02:08
>To: SQLite mailing list
>Subject: Re: [sqlite] Using CT
6
2
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected]] On Behalf Of pali
>Sent: Sunday,
Make sure to wrap your transactions in BEGIN / COMMIT. Use BEGIN IMMEDIATE for
transactions that you know are going to write, and plain BEGIN for read-only
transactions. You can omit the explicit BEGIN / COMMIT if each transaction
consists of only a single statement since autocommit will do a
By "constantly writing" I presume you mean "periodically writing". For example
doing one independent INSERT every millisecond where there is no dependency
from between inserts is "periodic writing". "Constantly writing", from a
database perspective, means a single transaction that never ends
Remember that date('now') is the UT1 date, not the local (wallclock) date. To
get the date 'now' for the timezone in which your computer thinks it is located
you need to add the 'localtime' qualifier, as in date('now', 'localtime') ...
---
The fact that there's a Highway to Hell but only a Sta
NFS is a Remote/Network File System.
iSCSI is a local file system.
iSCSI is just transporting the SCSI protocol over a "different" physical layer
sort of like how you can transport SCSI over really really fat parallel SCSI
cables, PATA cables, or SATA cables. (That is, pSCSI, sSCSI, and iSCS
single-quotes around the tablename -- it is a string not an identifier ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>[email protected].
;)
And I am stealing it back ... I like your changes that show the computed column
affinity!
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@m
The comparison is between a column with "numeric" (integer) affinity and a text
value with no affinity. The text value is an empty string.
Affinity conversion would attempt to convert the text value with no affinity
into a numeric value (0) IF AND ONLY IF the conversion is lossless and
reve
On Friday, 24 August, 2018 17:31, [email protected] wrote:
>"The parent key of a foreign key constraint is not allowed to use the
>rowid. The parent key must used named columns only."
>Why is this?
You should think of this as:
>"The parent key of a foreign key constraint is not allowed to use the
>ro
1 - 100 of 2009 matches
Mail list logo
