Groups | Search | Server Info | Login | Register
Groups > comp.lang.tcl > #55680
| From | Rich <rich@example.invalid> |
|---|---|
| Newsgroups | comp.lang.tcl |
| Subject | Re: Optimal used of sqlite |
| Date | 2026-04-29 21:54 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10stulo$83nr$1@dont-email.me> (permalink) |
| References | <10st8ah$14ekd$1@tota-refugium.de> <10st9d0$156i$1@dont-email.me> <10stebq$15qud$2@tota-refugium.de> |
meshparts <alexandru.dadalau@meshparts.de> wrote: > Am 29.04.2026 um 17:50 schrieb Rich: >> Care to define what "llength" constitutes "large" for you? > > Well, the size of the list is anything between 1e3 to 1e9 as an order of > magnitude. I presume you mean 10e3 to 10e9, as 1 to the third power, and 1 to the ninth power, are both one... :) Yes, those that approach 10e9 in length will consume a significant amount of time creating the string serialization, which sqlite has to unparse to then insert into the column.
Back to comp.lang.tcl | Previous | Next — Previous in thread | Next in thread | Find similar
Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 17:32 +0200
Re: Optimal used of sqlite Rich <rich@example.invalid> - 2026-04-29 15:50 +0000
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 19:13 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 19:44 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 19:58 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 20:06 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 23:29 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 23:50 +0200
Re: Optimal used of sqlite rene <user4652@newsgrouper.org.invalid> - 2026-04-30 09:22 +0000
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 11:43 +0200
Re: Optimal used of sqlite rene <user4652@newsgrouper.org.invalid> - 2026-04-30 13:09 +0000
Re: Optimal used of sqlite Ralf Fassel <ralfixx@gmx.de> - 2026-04-30 15:35 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 15:49 +0200
Re: Optimal used of sqlite Rich <rich@example.invalid> - 2026-04-29 21:56 +0000
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 00:12 +0200
Re: Optimal used of sqlite Rich <rich@example.invalid> - 2026-04-29 22:22 +0000
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 08:00 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 08:34 +0200
Re: Optimal used of sqlite Ralf Fassel <ralfixx@gmx.de> - 2026-04-30 14:38 +0200
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-29 19:15 +0200
Re: Optimal used of sqlite Rich <rich@example.invalid> - 2026-04-29 21:54 +0000
Re: Optimal used of sqlite meshparts <alexandru.dadalau@meshparts.de> - 2026-04-30 00:08 +0200
Re: Optimal used of sqlite Julian Bradfield <jcb@inf.ed.ac.uk> - 2026-04-30 10:25 +0000
csiph-web