So...
`SELECT x FROM y WHERE x LIKE CONCAT('v', '%')` does not work
But
`SELECT x FROM y WHERE x LIKE 'v%'` does, as does
`SELECT x FROM y WHERE x LIKE 'v' || '%'`
Please. #Postgres and #PostgreSQL community, make it make sense???
Developer, harpist, time traveler from the moment right before this one; so don't ask me, I just got here.
It was still a stupid, stupid, stupid, stupid, stupid, stupid, stupid, stupid plan.
Languages | en;fr |
Pronouns | he/him |
Geo | 39.2904° N, 76.6122° W |
@jamie `VARCHAR(8)` (legacy system ported over from MySQL). I feel like I've seen it work before and used it myself, which is why I'm baffled.
I use PG16 in this case, but I feel the same, these aren't wacky new experimental features, they're string concatenation.
But anyhow, if it were a type/operator mismatch problem, and I'm not saying it's not, it's what I keep thinking but I can't see how, I'd expect an error, not a silent failure to return any reasonable data.
So...
`SELECT x FROM y WHERE x LIKE CONCAT('v', '%')` does not work
But
`SELECT x FROM y WHERE x LIKE 'v%'` does, as does
`SELECT x FROM y WHERE x LIKE 'v' || '%'`
Please. #Postgres and #PostgreSQL community, make it make sense???
The Trump admin has cancelled the panels that approve NIH grants, and is also banning scientists from communicating with the public, attending conferences, and hiring.
The NIH is the largest public funder of biomedical research in the world. This will severely halt the development of many lifesaving treatments. Absolutely devastating.