> On Feb 28, 2019, at 3:14 PM, Wout Mertens wrote:
>
> It seems to me that it could be worthwhile to do transparent compression on
> JSON strings, perhaps using a differently trained dictionary…
Regular LZ/zip type compression already does a good job on JSON, even fairly
short bits. Not just
Wonderful!
Things I wonder:
* would it be possible to set up columns in such a way that the compression
is transparent, that is, existing queries remain unchanged?
* How does it fare on JSON strings? I notice that double-quotes are short,
but array and object delimiters are 11/12 bits?
It seems
I meant reflinks not extents. I should go to bed ;)
Wout.
On Thu, Feb 28, 2019 at 11:57 PM Wout Mertens
wrote:
> One option, if you are on a filesystem supporting extents (macOS's apfs
> and Linux's btrfs only, currently, with xfs and bcachefs support on the
> horizon): do a copy with reflinks
One option, if you are on a filesystem supporting extents (macOS's apfs and
Linux's btrfs only, currently, with xfs and bcachefs support on the
horizon): do a copy with reflinks (cp -c on macOS, cp --reflink=auto
elsewhere). That should be super fast since all it does is point to
existing data and
Dr. Hipp, I don't care what Simon says about you; you're ok in my book. ;-)
From: sqlite-users on behalf of Richard Hipp
Sent: Thursday, February 28, 2019 12:31 PM
To: SQLite mailing list
Subject: Re: [sqlite] TCL API: substitution of NULL for non-existent variables
On 2/28/19, Donald Allen wr
On 2/28/19, Donald Allen wrote:
> Is there a way to override the substitution of NULL for non-existent
> Tcl variables in a query?
https://www.sqlite.org/draft/tclsqlite.html#bind_fallback
This enhancement was checked in moments ago, so you will need to
rebuild from the latest trunk sources.
htt
On 28 Feb 2019, at 4:33pm, Donald Allen wrote:
> The difficulty with this is that there are fields in my database that *can*
> legitimately be NULL under certain circumstances and not NULL in others.
Is it possible to tell from the other fields in that row whether the NULL is
legit or not ? Y
On Thu, 28 Feb 2019 at 11:06, Jose Isaias Cabrera wrote:
>
>
>
> Hi. This is from a newbie, so take it with a grain of salt... :-)
Nahh -- happy to have your thoughts about this.
> There is always the DB field declaration of NOT NULL, but, if you are going
> to allow a NULL value in that field
Hi. This is from a newbie, so take it with a grain of salt... :-)
There is always the DB field declaration of NOT NULL, but, if you are going to
allow a NULL value in that field, then, h...
From: sqlite-users on behalf of Donald Allen
Sent: Thursday, February 28, 2019 08:35 AM
To: sqlite-
Is there a way to override the substitution of NULL for non-existent
Tcl variables in a query? I have been bitten by this many times, by
mis-typing the variable name in the query and having the query do the
wrong thing rather than failing outright. I think there ought to be an
option that throws an
On Thu, Feb 28, 2019 at 10:16 AM Richard Hipp wrote:
> On 2/28/19, Dominique Devienne wrote:
> > On Thu, Feb 28, 2019 at 12:14 AM Richard Hipp wrote:
> >> Docs have now been updated.
> >
> > Hi. I don't see it in https://www.sqlite.org/src/timeline.
> > Did I miss it? Or is that doc in some oth
On 2/28/19, Jean-Baptiste Gardette wrote:
>
> PS : on wich OS did you run the test script ?
> (the different outputs between the two computers gives
> unconfortable feeling)
>
Linux
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing li
On 2/28/19, Dominique Devienne wrote:
> On Thu, Feb 28, 2019 at 12:14 AM Richard Hipp wrote:
>> Docs have now been updated.
>
> Hi. I don't see it in https://www.sqlite.org/src/timeline.
> Did I miss it? Or is that doc in some other repo?
For historical reasons, the SQLite documentation is in a
On Thu, Feb 28, 2019 at 12:14 AM Richard Hipp wrote:
> On 2/27/19, lnksz wrote:
> > 2) If not, a mention in the docs under disadvantages would be a
> nice information
>
> Docs have now been updated.
Hi. I don't see it in https://www.sqlite.org/src/timeline.
Did I miss it? Or is that doc in som
On Wed, Feb 27, 2019 at 9:20 PM Keith Medcalf wrote:
> [...] As such, except in OUTER joins, you do not even have to have the ON
> expression related to the table(s) which have been seen so far or even
> those in the join expression ...
because ON is merely a syntactic substitute for WHERE and m
15 matches
Mail list logo
