I mostly agree.
I mostly agree. I think sql's achilles heel in this regard is where prepared statement parameters are needed but aren't supported, or need a better representation - during bulk inserts, having to generate a list of values. It'd be wonderful to be able to just supply a single `?`, or use some other symbol to note that it's a value list. Making the user generate a bunch of (?,?),(?,?)... is not at all friendly, and something everyone has to do. and the cherry on top is that there can't be a dangling comma at the end, so it's gotta be chopped off, or omitted. Not at all a hard problem. It's an annoying problem that I don't understand why it hasn't been solved at the prepared statement level. - things like database, table, or column identifiers that may be variable based on application context Basically anywhere that currently winds up getting interpolated should have a way to be parameterized. without those two, i think it's inevitable to arrive at one of: - an orm - a sql query template renderer - a bunch of functions to do very specific string interpolations
Posted by chrsig on Sep 29, 2022, 2:56 PM
Tags
Related issues
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
- > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
hackernews (Other)
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
The biggest problem with plugging a generator into an outlet is you need a double ended cord.
I mostly agree.
I mostly agree. I think sql's achilles heel in this regard is where prepared statement parameters are needed but aren't supported, or need a better representation - during bulk inserts, having to generate a list of values. It'd be wonderful to be able to just supply a single `?`, or use some other symbol to note that it's a value list. Making the user generate a bunch of (?,?),(?,?)... is not at all friendly, and something everyone has to do. and the cherry on top is that there can't be a dangling comma at the end, so it's gotta be chopped off, or omitted. Not at all a hard problem. It's an annoying problem that I don't understand why it hasn't been solved at the prepared statement level. - things like database, table, or column identifiers that may be variable based on application context Basically anywhere that currently winds up getting interpolated should have a way to be parameterized. without those two, i think it's inevitable to arrive at one of: - an orm - a sql query template renderer - a bunch of functions to do very specific string interpolations
Comments (0)
No comments yet. Start the discussion.