> Why is there no ORM that works like this?
> Why is there no ORM that works like this? Because no one wants to write a SQL fragment parser. You would have write a parser that: a) Could be started at an arbitrary place in a query and figure out what it needed to do. b) Would be SQL-dialect aware. (Maybe -- it might be possible to skip this.) Were it not for (a), I'd imagine you could quickly build this by using some kind of debug feature of the database -- sending it a query to parse and getting back a parse tree.
Posted by solidsnack9000 on Mar 10, 2015, 11:21 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- 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?
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
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?
> Why is there no ORM that works like this?
> Why is there no ORM that works like this? Because no one wants to write a SQL fragment parser. You would have write a parser that: a) Could be started at an arbitrary place in a query and figure out what it needed to do. b) Would be SQL-dialect aware. (Maybe -- it might be possible to skip this.) Were it not for (a), I'd imagine you could quickly build this by using some kind of debug feature of the database -- sending it a query to parse and getting back a parse tree.
Comments (0)
No comments yet. Start the discussion.