The following code does not work, but gives an idea what I want to do:
create table t (a, b);
select
group_concat(b) as list
from t
group by a
having ?1 in (list);
i.e. how to select only the groups that contain
some value in the set of values in a column not
Incidentally, Bedrock is built on a blockchain as well -- though I agree
with the sentiment that blockchain isn't actually new at all, and not that
big of a deal. More information is here:
http://bedrockdb.com/blockchain.html Hope you enjoy it!
-david
On Thu, Oct 11, 2018 at 3:06 PM R Smith
WARNING: the following sentence will be claimed to be controversial:
No database based on SQL is truly relational.
LOL - who would claim that to be controversial?
It doesn't spur controversy...
It's worthy of a shrug at best, perhaps a "So what?".
It sounds like a deepity - much like any
On Oct 11, 2018, at 2:25 PM, Eric wrote:
>
> On Thu, 11 Oct 2018 10:20:08 -0600, Warren Young wrote:
>> On Oct 11, 2018, at 12:26 AM, Darren Duncan wrote:
> 8><
>
>>> This makes me think that it would be useful, if it doesn't already,
>>> for Fossil to have something analogous to a
You are correct. Value should/ could be inside count(), but not in group.
Sent from my T-Mobile 4G LTE Device
Original message
From: R Smith
Date: 10/11/18 4:29 PM (GMT-05:00)
To: sqlite-users@mailinglists.sqlite.org
Subject: Re: [sqlite] Find key,value duplicates but
On Thu, 11 Oct 2018 14:37:47 -0600, "Keith Medcalf" wrote:
>
> Balderdash.
>
> > The interlocking of artifacts by cryptographic hashes does seem very much
> > like the same idea as blockchain, which Wikipedia says was invented in
> > 2008. It is interesting that the first Fossil checkin was 21
Balderdash.
> The interlocking of artifacts by cryptographic hashes does seem very much
> like the same idea as blockchain, which Wikipedia says was invented in
> 2008. It is interesting that the first Fossil checkin was 21 July, 2007
> (and the first git checkin was 7 April, 2005).
Hashed
On 2018/10/11 9:53 PM, Roman Fleysher wrote:
It is hard for me to tell which is index, which is value and so forth in your
example, but how about this single select:
SELECT DISTINCT key, value FROM theTable;
This lists all distinct key-value possibilities. Or,
SELECT key, value FROM (SELECT
Picking up a couple of sentences from a different thread, just for a
reference point really, please feel free to ignore ...
On Thu, 11 Oct 2018 10:20:08 -0600, Warren Young wrote:
> On Oct 11, 2018, at 12:26 AM, Darren Duncan wrote:
8><
>> This makes me think that it would be useful,
It is hard for me to tell which is index, which is value and so forth in your
example, but how about this single select:
SELECT DISTINCT key, value FROM theTable;
This lists all distinct key-value possibilities. Or,
SELECT key, value FROM (SELECT DISTINCT key, value FROM theTable)
GROUP BY
For interactive work in the CLI anyway there's the .tables command and the
.schema command
https://www.sqlite.org/cli.html#querying_the_database_schema
The first will show all the tables and views
The second will give you the SQL stored for the table and its indexes, etc.
-Original
Hello,
I'd like to ask whether it would be possible to add support for MySQL-style
SHOW command, i.e.
- SHOW TABLES [FROM db_name]
- SHOW COLUMNS FROM table
I know that this information can be retrieved in other ways, but imho SHOW is
an easy-to-remember statement and could simplify things a
On 2018/10/11 5:59 PM, Dominique Devienne wrote:
I can find duplicates fine:
select xmd.partId, parts.title, xmd.name,
count(*) "#dupplicates",
group_concat(xmd.value) "values",
group_concat(xmd.idx) "indexes"
from extra_meta_data xmd
join parts on parts.id =
Amen.
I'm about ready to unsubscribe from this list and not come back until it
transitions to a forum (which is the interface I prefer anyways) because of
all this nattering clogging up my inbox the last few days. I thought I was
a grumpy old fart set in my ways, but I don't have anything on some
On Oct 11, 2018, at 12:06 AM, Random Coder wrote:
>
> On Wed, Oct 10, 2018 at 3:45 PM Warren Young wrote:
>> The salt is the project code combined with the user ID, not a secret
>> per-user salt. Both of those values are publicly visible, but it does
>> defeat rainbow table attacks, which is
Maybe
...
group by partId, name
having count(distinct xmd.value) > 1;
?
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of Dominique Devienne
Sent: Thursday, October 11, 2018 12:00 PM
To: General Discussion of SQLite Database
On Thu, 11 Oct 2018 09:51:15 -0500, Balaji Ramanathan
wrote:
>>
>>2. Re: SQLite mailing list
>>
>
> The 1990's called and they want their mailing lists back. So, let us
> switch to 21st century technology already.
New is not necessarily better, old is not necessarily worse. Those who
Two nested selects
The inner select groups by partId, name, value
The outer select groups by partId, name
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Dominique Devienne
Gesendet: Donnerstag, 11. Oktober 2018 18:00
An:
On Oct 11, 2018, at 12:26 AM, Darren Duncan wrote:
>
> On 2018-10-10 1:36 PM, Eric wrote:
>> Too much overhead, how often must I clone ...
>
> This makes me think that it would be useful, if it doesn't already, for
> Fossil to have something analogous to a database replication feature.
That’s
I can find duplicates fine:
select xmd.partId, parts.title, xmd.name,
count(*) "#dupplicates",
group_concat(xmd.value) "values",
group_concat(xmd.idx) "indexes"
from extra_meta_data xmd
join parts on parts.id = xmd.partId
group by partId, name
having "#dupplicates" >
>
>2. Re: SQLite mailing list
>
>
The 1990's called and they want their mailing lists back. So, let us
switch to 21st century technology already. Count me in as an enthusiastic
YES vote for proper forums (including subforums - so that I can read what I
want and skip the rest instead of
On Wed, 10 Oct 2018 16:00:02 -0600, Warren Young wrote:
8><
There comes a point in any written discussion where point-by-point
answers become a risk to sanity. I think we are there.
It seems that a Fossil forum will someday be able to behave like a mailing
list. Good, but if the price
Darren Duncan wrote:
> On 2018-10-10 10:51 AM, Chris Green wrote:
> > Warren Young wrote:
> >> Fossil forum email alerts include the full content of the message.
>
> That's great! Especially if the alert email subject includes the forum
> thread
> subject.
>
> That said, I consider it
On Thursday, 11 October, 2018 00:22, Darren Duncan
wrote:
>On 2018-10-10 12:26 PM, Keith Medcalf wrote:
>> And if you think that I am going to create YET ANOTHER LOGIN and
>> YET ANOTHER PASSWORD just to use some crappy forum software, you have
>> another think coming.
> What do you think
On 2018-10-10 1:36 PM, Eric wrote:
Too much overhead, how often must I clone ...
This makes me think that it would be useful, if it doesn't already, for Fossil
to have something analogous to a database replication feature. A bit like a
mailing list but that the sender and client are both
On 2018-10-10 12:26 PM, Keith Medcalf wrote:
And if you think that I am going to create YET ANOTHER LOGIN and YET ANOTHER
PASSWORD just to use some crappy forum software, you have another think coming.
What do you think password managers are for? Proper security means having a
different
On 2018-10-10 10:51 AM, Chris Green wrote:
Warren Young wrote:
Fossil forum email alerts include the full content of the message.
That's great! Especially if the alert email subject includes the forum thread
subject.
That said, I consider it critical that these alert emails can also send
On Wed, Oct 10, 2018 at 3:45 PM Warren Young wrote:
> Fossil currently has no restrictions on password length[1] or content. The
> input text is simply salted, hashed, and inserted into the user table:
> [...]
> The salt is the project code combined with the user ID, not a secret per-user
>
28 matches
Mail list logo
