On 2/16/16, Denis Burke wrote:
>
> select case when null not in ('a') then 'not in list' else 'is in list'
> end;
>
The expression "null not in ('a')" evaluates to null. So your query
is really: "select case when null then 'not-in-list' else
'is-in-list' end;" Since the condition is not true
I realize that SQLite will handle NULLs according to:
https://sqlite.org/nulls.html
As best as I can tell this is a case not listed on that page and gives an
answer different than I would expect:
select case when null not in ('a') then 'not in list' else 'is in list' end;
This gives "is in
On Tuesday, 16 February, 2016 20:33. Denis Burke asked:
> I realize that SQLite will handle NULLs according to:
> https://sqlite.org/nulls.html
> As best as I can tell this is a case not listed on that page and gives an
> answer different than I would expect:
What answer do you expect? Why do
The quality and helpfulness of this mailing list makes me wish for a
SQHeavy...
IME when SQLite is applicable (mostly the one writer limit), it usually
runs circles around to server DBs, provided:
- you have comparable CPU
- you have enough cache memory, or free RAM for OS disk caching, to be in a
comparable memory scenario
- you do not have a virtualisation layer, especially
Hello,
I connect to the same database file twice, first in readonly mode and
then in readwrite mode while having set sqlite3_enable_shared_cache(1).
Any attempt to change any data using the second database connection
results in an "attempt to write a readonly database" error.
The same code
On 2/16/16, Roger Binns wrote:
>
> The way I (and many others) do it is to use the user_version. It is
> an integer that starts out as zero, and can be read or written with
> pragma user_version. Startup code then looks like this:
>
> if user_version()==0 {
> BEGIN;
> CREATE TABLE
obviously it will never be perfect . We already know the benefits of
each database , including those of SQLITE . This is not because there is
a benchmark that people are not going to look at all the other features.
But in equal hardware, it gives a small indication of current
performance, as
On Mon, 15 Feb 2016 14:19:12 -0700
Scott Robison wrote:
> Each job will take some amount of time to process. The order doesn't
> matter as long as all jobs are eventually processed and you have a
> single process running the jobs. Limit 1 is a reasonable way to grab
> a single job.
Reasonable,
On Mon, 15 Feb 2016 14:55:34 -0700
"Keith Medcalf" wrote:
> Pretty sure you meant:
>
> select * from (select min(t) as t from T) as T;
Yes, thanks. :-)
--jkl
On 16 Feb 2016, at 11:08am, Klaas Van B. wrote:
> N.N. wrote Mon, 15 Feb 2016 09:19:11 +0800:
>
>> Why SQLite does not utilize a web-based forum for all users discuss
>> problems? I think that will be more convenient and can help more people.
>
> LinkedIn (https://www.linkedin.com) has two:
On 16 Feb 2016, at 6:30am, olivier vidal wrote:
> It would be great if someone could redo these tests with the current versions
> of the databases.
On what hardware ? Should the SQLite test be on a laptop because SQLite will
run on a laptop ? Or should you test both on identical hardware
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/02/16 01:01, Luca Ferrari wrote:
> While I'm pretty sure a simple sheel script that will execute,
> file per file, the alter table (within a transaction) will do the
> job I'm wondering if there's a better approach or a more automated
> one.
On Tue, Feb 16, 2016 at 11:44 AM, James K. Lowden
wrote:
> On Mon, 15 Feb 2016 14:19:12 -0700
> Scott Robison wrote:
>
> > Each job will take some amount of time to process. The order doesn't
> > matter as long as all jobs are eventually processed and you have a
> > single process running the
On https://www.sqlite.org/datatypes.html there is a typographical error.
In the first paragraph of 1.0 Typelessness
"A database is suppose to store and retrieve data and it should? the word
should be ?supposed"
N.N. wrote Mon, 15 Feb 2016 09:19:11 +0800:
>Why SQLite does not utilize a web-based forum for all users discuss
>problems? I think that will be more convenient and can help more people.
LinkedIn (https://www.linkedin.com) has two: "SQLite" and "SQLite Professional"
and I'm pretty sure that on
Good thread,
which absolutely nails the point 'dev decisions for app cases' make a
developers world go round. I personally couldn't think of a greater waste
of time than a benchmark comparison between client server rdbms's and
sqlite. Do what benefits your case most. The above from Jim pretty
It would be great if someone could redo these tests with the current
versions of the databases.
Jim Callahan a ?crit :
> There is a historical and unfair (specially compiled version of SQLite
> against default settings of PostgreSQL) benchmark
> available on this page, but now that you
18 matches
Mail list logo
