On 27-1-2020 23:18, Richard Hipp wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural term to use, as it
> seems to mean "without a server".
>
Maybe "edge" database ? Or "local" database ? Both are trending terms, on
the theme of taking control and performance back from the cloud.
"Embedded" would be technically good, but is often associated with devices
and small things these days.
Le mar. 28 janv. 2020 à 05:58, Rowan Worth a écrit
On Tue, 28 Jan 2020 at 06:19, Richard Hipp wrote:
> Note that "in-process" and "embedded" are not adequate substitutes for
> "serverless". An RDBMS might be in-process or embedded but still be
> running a server in a separate thread. In fact, that is how most
> embedded RDBMSes other than
On Mon, Jan 27, 2020 at 05:18:45PM -0500, Richard Hipp wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural term to use, as it
...
> So what do I call
Edit, that last part should say "skim server" :D
On Mon, Jan 27, 2020, 10:54 PM David Baird wrote:
> How about "skim server"? So if, "server" means a whole server, then like
> whole milk versus skim milk, a fraction of a server becomes severless :)
>
> On Mon, Jan 27, 2020, 9:57 PM Stephen
How about "skim server"? So if, "server" means a whole server, then like
whole milk versus skim milk, a fraction of a server becomes severless :)
On Mon, Jan 27, 2020, 9:57 PM Stephen Chrzanowski
wrote:
> I'd stick with "serverless". The marketing teams that make "serverless"
> mean that
I'd stick with "serverless". The marketing teams that make "serverless"
mean that websites don't run with "servers" are I-D-TEN-Ts. It's a fad
phrase that'll go away eventually. I understand marketing, and its
purpose, but, in this case, they're pushing it.
On Mon, Jan 27, 2020 at 9:31 PM sub
Also maybe Slipstreamed?
-Neal
On Monday, January 27, 2020, sub sk79 wrote:
> How about Seamless, Integrated or Baked-in?
>
> -Neal
>
> On Monday, January 27, 2020, Warren Young wrote:
>
>> On Jan 27, 2020, at 3:18 PM, Richard Hipp wrote:
>> >
>> > "serverless" has become a popular buzz-word
Standalone (library / database provider )
native
header-only (almost)
there's an entry on 'standalone programs' in wikipedia, and there's lots of
other libraries that have standalone versions, but it's not a very well
defined word.
in-process is probably closest (in-process database
SQLite is your everywhere database, except on servers ;)
On Mon, Jan 27, 2020 at 9:12 PM sub sk79 wrote:
> How about Seamless, Integrated or Baked-in?
>
> -Neal
>
> On Monday, January 27, 2020, Warren Young wrote:
>
> > On Jan 27, 2020, at 3:18 PM, Richard Hipp wrote:
> > >
> > > "serverless"
How about Seamless, Integrated or Baked-in?
-Neal
On Monday, January 27, 2020, Warren Young wrote:
> On Jan 27, 2020, at 3:18 PM, Richard Hipp wrote:
> >
> > "serverless" has become a popular buzz-word that
> > means "managed by my hosting provider rather than by me.”
>
> “Serverless” it a
> On Jan 27, 2020, at 2:18 PM, Richard Hipp wrote:
>
> But more recently, "serverless" has become a popular buzz-word that
> means "managed by my hosting provider rather than by me."
I hate this buzzword. It's especially confusing because peer-to-peer
architectures are also validly
On Jan 27, 2020, at 3:18 PM, Richard Hipp wrote:
>
> "serverless" has become a popular buzz-word that
> means "managed by my hosting provider rather than by me.”
“Serverless” it a screwy buzzword anyway, because of course there’s still a
server under its new meaning.
My vote? Keep using the
I'll throw in "embedded", but I'd vote for "self contained" too :-)
> On 27. Jan 2020, at 23:57, Jay Kreibich wrote:
>
> I often describe it as “self contained.”
>
> -j
>
> Sent from my iPhone
>
>> On Jan 27, 2020, at 4:19 PM, Richard Hipp wrote:
>>
>> For many years I have described
In C/C++ the closest concept is a Header Only Library.
Except that SQLITE is not only C+++, and it's not header only...
Library Only Implementation?
In-Proc / In-Thread Library?
Self Contained Library?
Looks like I'm on a generally "Library" theme here...
- Deon
-Original Message-
"When I use a word,' Humpty Dumpty said in rather a scornful
tone, 'it means just what I choose it to mean - neither more nor
less.'
'The question is,' said Alice, 'whether you can make words mean
so many different things.'
'The question is,' said Humpty Dumpty, 'which is to be master -
that's
On 27 Jan 2020, at 11:53pm, Donald Shepherd wrote:
> In-process? Same concept but defining it by what it is rather than what it
> isn't.
This comes closest to what I think needs stating. What you're trying to say is
that there's no process (on the accessing computer or some other computer
Server-free sounds good. Standalone too. Integrated maybe?
On Mon, Jan 27, 2020, 17:54 Donald Shepherd
wrote:
> On Tue, 28 Jan 2020 at 10:19 am, Richard Hipp wrote:
>
> > daemon-less?
> > --
> > D. Richard Hipp
> > d...@sqlite.org
>
>
> In-process? Same concept but defining it by what it is
On Tue, 28 Jan 2020 at 10:19 am, Richard Hipp wrote:
> daemon-less?
> --
> D. Richard Hipp
> d...@sqlite.org
In-process? Same concept but defining it by what it is rather than what it
isn't.
Regards,
Donald Shepherd.
>
___
sqlite-users mailing
"Server-free"? It's reasonably close to serverless, but doesn't have the
conflicting meaning.
Jen
On Mon, Jan 27, 2020 at 05:18:45PM -0500, Richard Hipp wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server
daemon-less?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Define what "serverless" means to you in the SQLite context and provide
a link or pop-up to that definition wherever "serverless" occurs in the
documentation. Perhaps also include what it doesn't mean if you think
this is becoming an issue.
How others choose to define "serverless" should not
standalone seems reasonable.
To confuse things further, I have seen Sqlite embedded in an embedded
web server, serverless doesn't fit that case.
On Tue, Jan 28, 2020 at 9:45 AM Jose Isaias Cabrera wrote:
>
>
> Richard Hipp, on Monday, January 27, 2020 05:18 PM, wrote...
> >
> > For many years
I often describe it as “self contained.”
-j
Sent from my iPhone
> On Jan 27, 2020, at 4:19 PM, Richard Hipp wrote:
>
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless"
Richard Hipp, on Monday, January 27, 2020 05:18 PM, wrote...
>
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural term to use, as it
> seems to mean
I think of it as being "standalone."
Gerry Snyder
On Mon, Jan 27, 2020, 3:19 PM Richard Hipp wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural
On 27 Jan 2020, at 22:18, Richard Hipp wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural term to use, as it
> seems to mean "without a server".
>
>
Runtimeless?
Not sure if the word runtimeless would be accurate to describe SQLite.
I'm not sure if it is even a word, I'm not a native english speaker.
But here is my contribution.
On Mon, Jan 27, 2020 at 7:19 PM Richard Hipp wrote:
> For many years I have described SQLite as being
Client (only) db
Sequential db
On Mon, Jan 27, 2020, 5:27 PM Peter da Silva wrote:
> Local?
>
> On Mon, 27 Jan 2020, 16:19 Richard Hipp, wrote:
>
> > For many years I have described SQLite as being "serverless", as a way
> > to distinguish it from the more traditional client/server design of
>
Local?
On Mon, 27 Jan 2020, 16:19 Richard Hipp, wrote:
> For many years I have described SQLite as being "serverless", as a way
> to distinguish it from the more traditional client/server design of
> RDBMSes. "Serverless" seemed like the natural term to use, as it
> seems to mean "without a
I like "NO-SERVER"
-Original Message-
From: Richard Hipp
To: General Discussion of SQLite Database
Sent: Mon, Jan 27, 2020 2:18 pm
Subject: [sqlite] New word to replace "serverless"
For many years I have described SQLite as being "serverless", as a way
to distinguish it from the more
For many years I have described SQLite as being "serverless", as a way
to distinguish it from the more traditional client/server design of
RDBMSes. "Serverless" seemed like the natural term to use, as it
seems to mean "without a server".
But more recently, "serverless" has become a popular
On Monday, 27 January, 2020 10:31, James K. Lowden
wrote:
>On Sun, 26 Jan 2020 12:01:32 -0700
>"Keith Medcalf" wrote:
>> Now that the table exists, use "SELECT * FROM " to determine
>> the number of columns in the table (which will include computed
>> always columns, if any).
>...
>>
On Sun, 26 Jan 2020 12:01:32 -0700
"Keith Medcalf" wrote:
> Now that the table exists, use "SELECT * FROM " to determine
> the number of columns in the table (which will include computed
> always columns, if any).
...
> Otherwise, Richard *may* make some changes to the .import logic which
>
On 1/27/20, Ondrej Dubaj wrote:
> The problem appears to be only on this arches.
That probably means it is an EBCDIC problem.
We have no way of replicating or debugging this problem as we have no
access to an s390 machine. Can RedHat perhaps provide one of the
SQLite developers with a
David Raymond, on Monday, January 27, 2020 10:32 AM, wrote...
[clip]
> (c.WYear = 2020) is a perfectly valid expression... that's returning a
> boolean (well, int)
> So you're comparing c.WYear (from the subquery) against a boolean.
Yep, this little bit I knew. :-)
> (Others have replied with
This is technically valid CASE syntax which is why you're not getting an error,
it's just not what you're looking for.
...
CASE
(SELECT c.WYear FROM t2 WHERE pid = a.a)
WHEN c.WYear = 2020 THEN “YES” ELSE “NO” END
) AS DIGITAL
...
What that is saying is take the value you get from this:
(SELECT
Jose Isaias Cabrera, on Monday, January 27, 2020 08:42 AM, wrote...
>
>
> Keith Medcalf, on Monday, January 27, 2020 04:02 AM, wrote...
This is actually what I need:
SELECT a.a,
a.c,
a.e,
b.g,
b.h,
b.i,
coalesce((
SELECT
Keith Medcalf, on Monday, January 27, 2020 04:02 AM, wrote...
>
>
> This version generates the most efficient query plan in 3.31.0 when you
> have indexes on the necessary columns:
>
> CREATE INDEX t0_1 on t0 (a, idate, c); -- c does not have to be in the
> index
> CREATE INDEX t1_1 on t1 (f,
Keith Medcalf, on Monday, January 27, 2020 02:28 AM, wrote...
>
>
> Do you perhaps mean:
>
> SELECT a.a,
> a.c,
> a.e,
> b.g,
> b.h,
> b.i,
> coalesce((
>SELECT 'YES'
> FROM t2
>
Except that should be for the header bytes only. It is somewhat inaccurate
because IEEE doubles may be stored as varints and values 0 and 1 may be stored
as just the header code 8 or 9 without storing the actual varint (if the schema
version is 4 or more, which cannot be read in an extension,
Keith Medcalf, on Sunday, January 26, 2020 11:19 PM, wrote...
>
>
> I get nothing at all except a complaint that the syntax is invalid. In
> particular
>
> (
> CASE
> (
> SELECT WYear FROM t2 WHERE pid = a.a
> )
> WHEN c.WYear = 2020 THEN “YES”
> ELSE “NO” END
> ) AS
Simon Slavin, on Sunday, January 26, 2020 09:59 PM, wrote...
>
> On 27 Jan 2020, at 2:44am, Jose Isaias Cabrera
> wrote:
>
> > CASE
> >(
> > SELECT WYear FROM t2 WHERE pid = a.a
> >)
> >WHEN c.WYear = 2020 THEN “YES”
> >ELSE “NO” END
>
> That's not the structure of a
You are missing
maxsize += _varIntSize_(maxsize)
fort he size varint at the begin oft he header just before the return
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Keith Medcalf
Gesendet: Montag, 27. Januar 2020 12:43
Hi,
I came across a problem during mate test, where fuzzcheck ends with
segfault.
The problem appears to be only on this arches. Other architectures are
working fine.
Build here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=40950404
Log:
./fuzzcheck
Here is a wee bit of C code that you can compile as a plugin that will give you
the row size (well, it may be bigger than the actual record size by a few bytes
but it is pretty close) ...
works properly for utf-16 encoded databases as well.
-//- sqlsize.c -//-
#include
You can certainly get the max and average cell size per page of rows from
dbstat which is the most granular data available I think, as well as the
average and max for all the rows taken together. Assuming that the table is a
"rowid" table, then that is the data for the "leaf" pages only. As
This version generates the most efficient query plan in 3.31.0 when you have
indexes on the necessary columns:
CREATE INDEX t0_1 on t0 (a, idate, c); -- c does not have to be in the index
CREATE INDEX t1_1 on t1 (f, idate);
CREATE INDEX t2_1 on t2 (pid, wyear); -- this could be a without rowid
As previously mentioned, SQLite uses a compressed format to store rows. You
would have to reverse engineer at least the calculation
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Deon Brewis
Gesendet: Samstag, 25. Januar
49 matches
Mail list logo