What happened with the electricity thing an self driving cars?
What happened with the electricity thing an self driving cars?
I won’t say they’re not making it up, but their screenshot has “AI overview”, yours doesn’t. It is probable that “normal” google gives different results than “AI” Google.
People mentioned a lot of things. I’ll add that plex doesn’t offer hardware transcoding without premium. Now, setting up hardware transcoding on an NVidia graphics card on linux is a bit complicated, setting it up on windows is really simple. While it’s not just clicking “enable hardware acceleration”, it’s not much more complicated than that.
Yes, also, mice are obviously female.
Mac is talking and denying any wrongdoing on Michael’s part.https://www.unilad.com/celebrity/macaulay-culkin-michael-jackson-inappropriate-behaviour-712982-20230423
Regarding RCD, where I live they’re allowed to be 30mA for wires that do not include outlets, but if an outlet is connected to the switch, the switch must cut off at 3mA…
Regarding the outlets, the type C is old, I haven’t seen those installed or sold since at least the early nineties (probably even earlier). I don’t understand why it being reversible is bad. I think switches can just cut of both wires, and you’re left with the ability to plug it in any way you like. I don’t really know whether the switches actually do that or not (or, if they’re required to do that). Can this be tested somehow?
In relational databases (sql) tables are actually table representations of relations, where a relation is defined as any subset of a Cartesian product.
In the first sql example we have a “person” relation, which is a subset of namesXgenders cartesian product. Because of this an element of the person relation (“Jimothy”, null) cannot have “no gender” (as it wouldn’t be a member of the cartesian product namesXgenders).
All of this leads to the following: null in sql doesn’t mean “said element doesn’t have that property”, it means that said property is unknown.
With that in mind, the first example returns expected, if on the surface counterintuitive result: you don’t know what Jimothy 's gender is, so when queried with NOT M NOT F, that row shouldn’t be returned, because you can’t just assume Jinothy’s gender. The query should be, for those cases: not m, not f or unknown (ie is null).
Similarly for the second case. Email is not nonexistent, it’s unknown, so it makes sense that the db allows you to insert more than one person with unknown email addresses.
I wouldn’t say that either of these is an sql wtf, I would just call both of those tables badly designed.