Keith,
Good point. Did not know this exists.
Ken
On 01/10/2017 09:48 PM, Simon Slavin wrote:
On 11 Jan 2017, at 1:02am, Keith Medcalf wrote:
You are correct, however, if there were a unique constraint placed on
tracks.name, then a given track could only appear once
Domingo,
Thanks for the email, but I don't think I am your inteded recipient.
Ken
On 01/10/2017 12:11 PM, Domingo Alvarez Duarte wrote:
Hello Richard !
Now that you are dealing with this ticket
http://www.sqlite.org/src/info/c92ecff2ec5f1784 could be a good moment
to acknowledge the
Keith,
"this does not allow the same track on multiple albums" with the same trackno,
but a different trackno seems to work. Thus results cannot be guaranteed valid?
Ken
On 01/08/2017 06:57 AM, Keith Medcalf wrote:
On Sunday, 8 January, 2017 05:05, Ken Wagner <beauco...@gma
Yes, thanks.
The 'left join on' or 'inner join on ' removes the chance of an
erroneous key linkage.
Also makes sense to pay close attention as to which table is left and
right.
Ken
On 01/09/2017 06:46 AM, Dominique Devienne wrote:
On Sun, Jan 8, 2017 at 12:46 PM, Keith Medcalf
TheFirstAndTheSecondTable =
TheSecondTableToBeJoined.TheCommonColumnNameBetweenTheFirstAndTheSecondTable;
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
On Behalf Of Ken Wagner
Sent: Sunday, 8 January, 2017 04:04
To: SQLite mailing list
Subject: Re: [
/2017 04:47 AM, Kees Nuyt wrote:
On Sun, 8 Jan 2017 04:21:16 -0600, Ken Wagner
<beauco...@gmail.com> wrote:
Hello SQLusers,
The error below occurs even though the
CREATE TABLE track(
trackid INTEGER,
trackname TEXT,
trackartist INTEGER,
*FOREIGN KEY(trackartist) REFE
Hello SQLusers,
The error below occurs even though the
CREATE TABLE track(
trackid INTEGER,
trackname TEXT,
trackartist INTEGER,
*FOREIGN KEY(trackartist) REFERENCES artist(artistid)*
);
statement at https://sqlite.org/foreignkeys.html was observed.
It appears that
David,
Yes. That would be a big assist. I am new to using SQLite3 and found the
GLOB function erratic in practice -- not on SQLite3 but on other web
sites using SQLite. They yielded completely opposite results.
Second the motion.
Ken
On 01/05/2017 05:23 PM, dandl wrote:
From:
Danap,
I thought so, too. But it is not the case.
I am cross-checking with the Unix/SQLite results, using Unix/SQLite as
the base reference.
Ken
On 01/05/2017 01:30 PM, dmp wrote:
Message: 21
Date: Wed, 4 Jan 2017 22:10:59 -0600
From: Ken Wagner <beauco...@gmail.com>
To: SQLite m
Smith wrote:
On 2017/01/05 9:04 AM, Ken Wagner wrote:
Keith,
It appears that the folks at SQLiteTutorial.net have a coding anomaly.
They are not following the UNIX / SQLite3 GLOB patterns. And so, too,
do the other guys.
I am adjusting my usage accordingly. I will advise users of the other
Keith,
It appears that the folks at SQLiteTutorial.net have a coding anomaly.
They are not following the UNIX / SQLite3 GLOB patterns. And so, too, do
the other guys.
I am adjusting my usage accordingly. I will advise users of the other
products to NOT use the GLOB "*[^1-9]*" pattern.
... print row
...
Row(sqlite_version=u'3.17.0', sqlite_source_id=u'2017-01-04 04:18:00
80ad317f89c46db0d0d252aefdc036a34a61183d')
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
On Behalf Of Ken Wagner
Sent: Wednesday, 4 January, 2017 22
sqlite-users-boun...@mailinglists.sqlite.org]
On Behalf Of Ken Wagner
Sent: Wednesday, 4 January, 2017 21:24
To: SQLite mailing list
Subject: Re: [sqlite] SQLite3 Tutorial error
Aha! GLOB is an implementation of the UNIX Glob function. It just
borrows the regex character notation of [^1-9].
I hav
Aha! GLOB is an implementation of the UNIX Glob function. It just
borrows the regex character notation of [^1-9].
I have 3.15 and 3.16 CLIs installed. Trying any other CLI versions at
this point won't help for the customer. They will be using a SQLite3
GUI. I will explain the difference
Yes, I am beginning to understand that. SQLite3 is its own GLOB standard.
I will abide by that.
It is just very confusing when 5 other apps using SQLite as their DB
engine all report the opposite.
The SQLite versions they use are 3.9.2, 3.10.1, 3.11.0 and 3.13.0.
Example: the SQLite
On 4 Jan 2017, at 1:43pm, Ken Wagner <beauco...@gmail.com> wrote:
There is yet another product "DB Browser for SQLite" using SQLite v 3.9.2.
It, too, omits any row where name contains any char 1 thru 9. It appears
SQLite at one point did this as 'GLOB '*[^1-9]*'.
But it do
Ryan,
Both 'AB6' or '5AB' fail the '[^1-9]' test. So, too do 'New Vol 4' and
'#1'.
Ken
On 01/04/2017 07:57 AM, R Smith wrote:
On 2017/01/04 3:43 PM, Ken Wagner wrote:
Yes, I changed the query to NOT GLOB '*[1-9]*' and then it omitted
the 1-9 char-containing entries.
However the logic
Ryan,
The Regex description of '[^0-9]' states NOT any 0 thru 9 char in any
SINGLE char position. It can be amended to 1-9 or 3-7 or 1-4 as the user
sees fit.
Tested it using Ruby and Rubular, a Regex Tester.
HTH,
Ken
On 01/04/2017 07:57 AM, R Smith wrote:
On 2017/01/04 3:43 PM, Ken
for the info.
Ken
On 01/04/2017 07:57 AM, R Smith wrote:
On 2017/01/04 3:43 PM, Ken Wagner wrote:
Yes, I changed the query to NOT GLOB '*[1-9]*' and then it omitted
the 1-9 char-containing entries.
However the logic of 'zero or any chars, then any single char NOT 1
thru 9, then zero
.
It's doable. Just adds extra work requiring checking.
Thanks,
Ken
On 01/04/2017 07:54 AM, Simon Slavin wrote:
On 4 Jan 2017, at 1:43pm, Ken Wagner <beauco...@gmail.com> wrote:
There is yet another product "DB Browser for SQLite" using SQLite v 3.9.2. It,
too, omits an
nt in the Chinook DB (at "1979", that is) but they have nothing
else in common.
Cheers,
Ryan
On 2017/01/04 2:53 PM, R Smith wrote:
On 2017/01/04 7:17 AM, Ken Wagner wrote:
About 2/3 the way down the page at:
http://www.sqlitetutorial.net/sqlite-glob/ Get names without
[1-9].
select trackid,
ars SQLite at one point did this as 'GLOB '*[^1-9]*'.
But it does not do so now. Does SQLite3 provide a detailed syntax
description of the GLOB permutations honored (and, perhaps, those
deprecated?)
Thanks.
Ken Wagner
On 01/04/2017 07:13 AM, R Smith wrote:
Just one more point of clarity,
FireFox v 50.1.0 and it, too, omits
any # 1-9 in the query results using " GLOB '*[^1-9]*' ".
How to resolve??
Thanks.
On 01/04/2017 06:53 AM, R Smith wrote:
On 2017/01/04 7:17 AM, Ken Wagner wrote:
About 2/3 the way down the page at:
http://www.sqlitetutorial.net/sqlite-g
Thanks, Jens.
I will do that.
- Ken
On 01/04/2017 12:29 AM, Jens Alfke wrote:
On Jan 3, 2017, at 9:17 PM, Ken Wagner <beauco...@gmail.com> wrote:
About 2/3 the way down the page at:
http://www.sqlitetutorial.net/sqlite-glob/
<http://www.sqlitetutorial.net/sqlite-glob/>
think, but use
the sqlite app.)
But not in sqlite3 3.15.1 and 3.16.1.
This works as expected in sqlite3 (3.15.1 and 3.16.1 :
select trackid, name from tracks where name not GLOB '*[1-9]*'; Gets
names without [1-9].
On 01/03/2017 07:37 PM, Richard Hipp wrote:
On 1/3/17, Ken Wagner
and 3.16.1). Also tested using
Ruby 2.3.3 with ruby-sqlite extension.
Thanks,
Ken Wagner
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
26 matches
Mail list logo