I really didn't think that's correct--though it's been a few years since I did SQL regularly.
SELECT *
FROM articles
WHERE last_updated >= %s
AND created_at IS NOT NULL
UNION
SELECT *
FROM articles
WHERE id IN (1, 2, 3)
AND created_at IS NOT NULL
That should give a list of all articles updated after whatever date (regardless of ID), appended to a list of all articles where the ID is 1, 2, or 3 (regardless of when they were last updated). I would expect to see extra articles that only fit one criteria or the other, and also duplicate articles.
I included the join quote because an inner join would be the way to do this, rather than a union--though it would likely be less efficient than just filtering on the required parameters.
If I'm wrong here, I'd love an explanation of why.
A UNION concatenates result sets from two queries. But a UNION does not create individual rows from columns gathered from two tables.
A JOIN compares columns from two tables, to create result rows composed of columns from two tables.
People don't just look at the TV for an hour straight - they are doing other things, or second-screening, or having conversations, and multiple methods being available to pick up on the show dialog is helpful.
Wouldn't this make subtitles less useful rather than more? You can't see the subtitles if you're not just looking at the TV. For second-screening, it would be more helpful to listen to the audio while you're also scrolling Lemmy or whatever.
Yeah, it sounds like the real problem is lack of off-site backups. Bad password policies will certainly make it easier for ransomware gangs, but they're not the only thing that has to go wrong.
My guess is that was someone who was in the car, which could be responsible for the erratic driving that resulted in such a horrific situation. That's just a guess, though.
I think I've got right around there where I'm living now; that's part of what makes it hard to contemplate leaving the country, even though this place (US) is turning pretty terrifying: I know if I leave it'll take years to build up friendships like that again, if it ever even happens.
Scheduling would not be fine; under HIPAA "provision of healthcare" is considered PHI, so knowing that person x had their care at a certain time and place would be a problem.
I really didn't think that's correct--though it's been a few years since I did SQL regularly.
SELECT * FROM articles WHERE last_updated >= %s AND created_at IS NOT NULL UNION SELECT * FROM articles WHERE id IN (1, 2, 3) AND created_at IS NOT NULLThat should give a list of all articles updated after whatever date (regardless of ID), appended to a list of all articles where the ID is 1, 2, or 3 (regardless of when they were last updated). I would expect to see extra articles that only fit one criteria or the other, and also duplicate articles.
I included the join quote because an inner join would be the way to do this, rather than a union--though it would likely be less efficient than just filtering on the required parameters.
If I'm wrong here, I'd love an explanation of why.