Hi Eric,
Eric Abrahamsen writes:
> This is about putting some more example stuff on Worg about using Org
> and SQLite...
Please go ahead and add this -- no need to ask for permission, Worg is
not too sensible :)
Thanks,
--
Bastien
Stefan Nobis writes:
> Eric Abrahamsen writes:
>
>> I was confused in part because the "where exists (select *..." looks
>> like its main purpose is to return rows.
>
> Indeed that's the purpose: Restrict the set of rows upon which update
> acts on. Here I tried to reformat the statement a bit
Stefan Nobis writes:
> Eric Abrahamsen writes:
>
>> I was confused in part because the "where exists (select *..." looks
>> like its main purpose is to return rows.
>
> Indeed that's the purpose: Restrict the set of rows upon which update
> acts on. Here I tried to reformat the statement a bit
Eric Abrahamsen writes:
> I was confused in part because the "where exists (select *..." looks
> like its main purpose is to return rows.
Indeed that's the purpose: Restrict the set of rows upon which update
acts on. Here I tried to reformat the statement a bit in order to
emphasize its
"Thomas S. Dye" writes:
> Cancel that, I was looking at a cached version of the page.
I guessed that was what happened :)
Stefan Nobis writes:
> Eric Abrahamsen writes:
>
>> Okay, it's up. If anyone wants to explain to me the point of the
>> "where exists" clause in the SQL, I would be interested to hear. It
>> works as expected this way, but is that clause necessary?
>
> Yes, very necessary. Without it, all
Cancel that, I was looking at a cached version of the page.
Thanks again for the documentation.
All the best,
Tom
Thomas S. Dye writes:
Okay, it's up. If anyone wants to explain to me the point of
the
"where
exists" clause in the SQL, I would be interested to hear. It
works as
expected this
Okay, it's up. If anyone wants to explain to me the point of the
"where
exists" clause in the SQL, I would be interested to hear. It
works as
expected this way, but is that clause necessary?
The 'if exists' clause protects against an SQLite error raised if
you ask to delete a table that
Eric Abrahamsen writes:
> Okay, it's up. If anyone wants to explain to me the point of the
> "where exists" clause in the SQL, I would be interested to hear. It
> works as expected this way, but is that clause necessary?
Yes, very necessary. Without it, all ratings would be changed - the
two
"Fraga, Eric" writes:
> This looks quite useful and would be nice to have on Worg. Thanks.
Okay, it's up. If anyone wants to explain to me the point of the "where
exists" clause in the SQL, I would be interested to hear. It works as
expected this way, but is that clause necessary?
"Thomas S. Dye" writes:
> Aloha Eric,
>
> Good news. Yes, please feel free to update the Worg SQLite page.
>
> IIRC, you can get permission from Bastien to push changes and then you
> can edit Worg at will.
Cool! Bastien, can you help me get write access to Worg?
Thanks,
Eric
Aloha Eric,
Good news. Yes, please feel free to update the Worg SQLite page.
IIRC, you can get permission from Bastien to push changes and then
you can edit Worg at will.
All the best,
Tom
--
Thomas S. Dye
http://tsdye.online/tsdye
This looks quite useful and would be nice to have on Worg. Thanks.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
Hi all,
This is about putting some more example stuff on Worg about using Org
and SQLite...
Years ago I realized that Org tables weren't really practical as
"proper" databases, storing large quantities of information. As tempting
as it was to keep everything in-Org, the tables get pretty
14 matches
Mail list logo
