Simon Slavin, on Wednesday, November 13, 2019 05:27 PM, wrote...
> By the way, Keith, 'Medcalf' is possibly the oldest known English surname
> (13th Century) and indicates that one
> of your ancestors raised or slaughtered cows.
Researching my last name, Cabrera, I found out that it origin
On Wednesday, 13 November, 2019 17:18, Warren Young wrote:
>On Nov 13, 2019, at 11:31 AM, Simon Slavin wrote:
>> Don't substring searches help you more than sorted lists ?
>There’s a relevant question for this list: how do we do this efficiently?
>The naive solution involves a table scan.
>E
>"Please fix your last name: No spaces allowed!">By the way, Keith, 'Medcalf'
>is possibly the oldest known English surname
>(13th Century) and indicates that one of your ancestors raised or
>slaughtered cows.
Aye, but over here the apparent only version that anyone knows is with a t in
place of
>
>
Keith Medcalf, on Wednesday, November 13, 2019 05:19 PM, wrote...
>
> Its like the stupid "security questions" thing. I always answer them with a
> vulgarity.
I knew this!!
josé
___
sqlite-users mailing list
sqlite-users@mailinglists.sql
On 14 Nov 2019, at 12:18am, Warren Young wrote:
> Give up on names and use something else? (SSN, phone number, DOB…)
A growing number of organisations now ask me for my DOB or my postcode, rather
than my name, when looking me up. I think you just explained why. In my
country we have an incr
On Nov 13, 2019, at 11:31 AM, Simon Slavin wrote:
>
> Don't substring searches help you more than sorted lists ?
There’s a relevant question for this list: how do we do this efficiently? The
naive solution involves a table scan.
Enable FTS on that column?
Manual extraction into indexed looku
On Nov 13, 2019, at 3:47 PM, Peter da Silva wrote:
>
> the nurse wastes time looking me up some other way, and
> tells me I'm Peterda Silva.
My “Young II” saga probably burnt an hour of both my time and that of the
insurance company, since it required multiple calls to get it sorted. I use a
It just drew a red box and told me to fill out all fields.
Then I enter daSilva.
Worse are the ones that don't say anything and attach the 'da' somewhere
random without telling me.
Then I show up and the nurse wastes time looking me up some other way, and
tells me I'm Peterda Silva.
On Wed, 13
On 13 Nov 2019, at 9:56pm, Jose Isaias Cabrera wrote:
> We still need to know that it is your last name and not your first name, or
> 2nd name, or... :-) By the way, what do you do when the form says,
>
> "Please fix your last name: No spaces allowed!"
>
> Do you just type daSilva?
Peter's mi
On Wednesday, 13 November, 2019 14:56, Jose Isaias Cabrera
wrote:
>Peter da Silva, on Wednesday, November 13, 2019 04:37 PM, wrote...
>> My last name has a space in it. It's been less than a month since the
>> last time it was rejected by a form. One of my oldest online friends has
>> only one
Peter da Silva, on Wednesday, November 13, 2019 04:37 PM, wrote...
>
> My last name has a space in it. It's been less than a month since the last
> time it was rejected by a form. One of my oldest online friends has only
> one name. Assume nothing, permit everything.
We still need to know that it
My last name has a space in it. It's been less than a month since the last
time it was rejected by a form. One of my oldest online friends has only
one name. Assume nothing, permit everything.
On Wed, 13 Nov 2019, 15:23 Swithun Crowe,
wrote:
> Hello
>
> SS> Those are all excellent examples of wh
This looks to work fine and runs fast as well, combining the 2 queries I
have now:
UPDATE QR3PARAMS SET ED = CASE WHEN
ID IN
(SELECT ID FROM PROBLEMS WHERE
READ_CODE GLOB 'Eu522*' OR READ_CODE GLOB 'E2273*' OR READ_CODE =
'1777409015') OR
ID IN
(SELECT ID FROM CURRENT_MED WHERE
TERM_TEXT GLOB 'Sil
>
> This almost seems like a job for a view.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Actually, I still have 2 queries as before the one mentioned I have:
UPDATE QR3PARAMS SET ED =
(SELECT 1 FROM PROBLEMS WHERE
(READ_CODE GLOB 'Eu522*' OR READ_CODE GLOB 'E2273*' OR READ_CODE =
'1777409015')
AND ID = QR3PARAMS.ID LIMIT 1)
But I thought to keep matters simple (and maybe a bit faster
On Wednesday, 13 November, 2019 13:26, Bart Smissaert
wrote:
>Thanks, the second one does the job as I need 1 or 0 and no nulls.
>It saves me running 2 queries as before had:
>UPDATE QR3PARAMS SET ED = CASE WHEN ED = 1 THEN 1 ELSE
>(SELECT 1 FROM CURRENT_MED WHERE
>(TERM_TEXT GLOB 'Sildenafil
Thanks, the second one does the job as I need 1 or 0 and no nulls.
It saves me running 2 queries as before had:
UPDATE QR3PARAMS SET ED = CASE WHEN ED = 1 THEN 1 ELSE
(SELECT 1 FROM CURRENT_MED WHERE
(TERM_TEXT GLOB 'Sildenafil*' OR TERM_TEXT GLOB 'Tadalafil*' OR TERM_TEXT
GLOB 'Vardenafil*')
AND
Why not change it to something along the lines of:
UPDATE QR3PARAMS
SET ED = 1
WHERE
ED is not 1
AND EXISTS (
SELECT 1
FROM CURRENT_MED
WHERE
ID = QR3PARAMS.ID
AND (
TERM_TEXT GLOB 'Sildenafil*'
OR
TERM_TEXT GLOB 'Tadalafil*'
OR
TERM_TEXT GLOB 'Vardenafil*'
)
);
wh
Donald Griggs, on Wednesday, November 13, 2019 12:26 PM, wrote...
>
> >
> > When dealing with ED and sildenafil, getting a NULL result disappoints
> > everyone. ;-)
> >
Good one! NOT that **I** know anything about that. Hahahahah...
___
sqlite-use
Bart Smissaert, on Wednesday, November 13, 2019 12:22 PM, wrote...
>
> Yes, you right and have seen what happens.
> Indeed, does less update should say less updates to 1.
> Indeed, the clause "QR3PARAMS.ED = 1 is superfluous.
> I can see that in the second one the problem is with the update to nu
>
> When dealing with ED and sildenafil, getting a NULL result disappoints
> everyone. ;-)
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Yes, you right and have seen what happens.
Indeed, does less update should say less updates to 1.
Indeed, the clause "QR3PARAMS.ED = 1 is superfluous.
I can see that in the second one the problem is with the update to null.
All fixed now.
RBS
On Wed, Nov 13, 2019 at 5:01 PM Keith Medcalf wrote
Both queries update all rows in QR3PARAMS since there is no WHERE clause to
limit which rows are updated, so when you say "does less updates" what do you
mean, since it is manifestly impossible for one to do less updates than the
other -- both update every row or the table.
Secondly, in the fi
On 13 Nov 2019, at 8:25am, Wout Mertens wrote:
> - How do I create an email greeting
> - How do I create an address label
> - How should I sort a list of names
> - How should I show a logged in user
> - How do you let the user fill in their name
Wout is asking these question rhetorical
My data is the same, except ED has affinity integer and term_text affinity
text.
RBS
On Wed, 13 Nov 2019, 15:25 Jose Isaias Cabrera, wrote:
>
> Bart Smissaert, on Wednesday, November 13, 2019 06:41 AM, wrote...
> >
> > UPDATE QR3PARAMS SET ED =
> > CASE WHEN ED = 1 THEN 1
> > ELSE
> > (SELECT 1
David Raymond, on Wednesday, November 13, 2019 10:34 AM, wrote...
>
> "Why is ED changed to '' or NULL for ID 5?"
>
> When you update to a subquery which returns no rows, then the field gets
> updated to null.
So, I have to address "no matches or no rows returned" in another subquery.
Huh! Mu
"Why is ED changed to '' or NULL for ID 5?"
When you update to a subquery which returns no rows, then the field gets
updated to null.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listi
Bart Smissaert, on Wednesday, November 13, 2019 06:41 AM, wrote...
>
> UPDATE QR3PARAMS SET ED =
> CASE WHEN ED = 1 THEN 1
> ELSE
> (SELECT 1 FROM CURRENT_MED WHERE
> (QR3PARAMS.ED = 1 OR TERM_TEXT GLOB 'Sildenafil*' OR TERM_TEXT GLOB
> 'Tadalafil*' OR TERM_TEXT GLOB 'Vardenafil*')
> AND ID = QR3P
On 11/13/19 3:25 AM, Wout Mertens wrote:
> Fascinating discussion, and threads like this are why this is the only
> mailing list that always triggers my "important" flag :)
>
> My problem with names isn't the number of fields needed to present them (I
> liberally use JSON1), but the operations that
UPDATE QR3PARAMS SET ED =
CASE WHEN ED = 1 THEN 1
ELSE
(SELECT 1 FROM CURRENT_MED WHERE
(QR3PARAMS.ED = 1 OR TERM_TEXT GLOB 'Sildenafil*' OR TERM_TEXT GLOB
'Tadalafil*' OR TERM_TEXT GLOB 'Vardenafil*')
AND ID = QR3PARAMS.ID LIMIT 1) END
UPDATE QR3PARAMS SET ED =
(SELECT 1 FROM CURRENT_MED WHERE
(Q
Fascinating discussion, and threads like this are why this is the only
mailing list that always triggers my "important" flag :)
My problem with names isn't the number of fields needed to present them (I
liberally use JSON1), but the operations that are possible on them, and the
UI needed to enter
31 matches
Mail list logo
