Send-before-checking failure. :)
Corrections to my previous mail:
1. "... is to check in my code if the table exists" must read: "... is
to check in my code if the table is empty"
2. "...ON CONFLICT DO UPDATESET (Antenna..." must read: "...ON CONFLICT
DO UPDATE SET (Antenna..."
On 2020/02/24 06:17, Andy KU7T wrote:
Hi,
I would like to write a script that checks whether certain records already
exist, and if not, insert them. If they do exist, it should be a no op.
I am trying this:
IF (SELECT COUNT(*) FROM [Antennas]) = 0
BEGIN
/* Table data [Antennas] Record
SQLite is not a procedural language. IF is not a programming construct, it is
part of an expression.
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Andy KU7T
Gesendet: Montag, 24. Februar 2020 05:17
An: SQLite mailing
IF is not an SQL statement.
IF is a part of your host application programming language. It may also be
part of a proprietary vendor specific extension to the SQL language to permit
programmability such as the Sybase TRANSACT-SQL (licensed to Microsoft as
Microsoft SQL Server to run on
Hi,
I would like to write a script that checks whether certain records already
exist, and if not, insert them. If they do exist, it should be a no op.
I am trying this:
IF (SELECT COUNT(*) FROM [Antennas]) = 0
BEGIN
/* Table data [Antennas] Record count: 16 */
INSERT OR REPLACE INTO
Hello,
I didn't find this question in the mailing list archive (although it's
difficult to search).
Is there any plan to support materialized views?
By that I mean views whose result is stored permanently in a table and
that is updated automatically every time the underlying tables are
updated.
On 2/23/20 3:06 PM, R.Smith wrote:
On 2020/02/23 21:23, Richard Damon wrote:
On 2/23/20 8:31 AM, Olaf Schmidt wrote:
An amount of 140 tables in such a "BibleVersions.db" is not
uncommon and can be managed by SQLite in a good performance.
I'm not sure that form of division would be good.
On 23 Feb 2020, at 7:23pm, Richard Damon wrote:
> I'm not sure that form of division would be good. One basic rule of database
> normalization is that you don't break-up data based on the value of one of
> the fields because you can't make the table to lookup data from be taken from
> a field
On 2020/02/23 21:23, Richard Damon wrote:
On 2/23/20 8:31 AM, Olaf Schmidt wrote:
An amount of 140 tables in such a "BibleVersions.db" is not
uncommon and can be managed by SQLite in a good performance.
I'm not sure that form of division would be good. One basic rule of
database
Chip Beaulieu wrote:
> I also recently vacuumed the file. The issue really showed up after the FTS5
> was
> setup on the table. I suspect it’s got something to do with the triggers more
> than
> the indexes. I am definitely open to suggestions. I’ve not been able to find
> much
> info on
On 2/23/20 8:31 AM, Olaf Schmidt wrote:
Am 21.02.2020 um 02:24 schrieb Chip Beaulieu:
I have a table with 4.5 million records with full text indexing. >
Reads are very fast, but deleting / inserting / updating
takes on average about 50 seconds per record. I often do batches of
30,000 deletes
Am 21.02.2020 um 02:24 schrieb Chip Beaulieu:
I have a table with 4.5 million records with full text indexing.
> Reads are very fast, but deleting / inserting / updating
takes on average about 50 seconds per record.
I often do batches of 30,000 deletes / inserts at a time.
The last batch took
12 matches
Mail list logo
