this post was submitted on 11 Jun 2024
130 points (82.2% liked)
Programming
17699 readers
438 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It pointed out the exact problem immediately and would have saved hours of effort.
But yeah, it didn't know the name of the column and guessed at what it would be.
It made an incorrect inference, imagine how wrong it is on more complex questions.
Of course. I would not recommend using it.
More like giving hints or a rough frame to work with.
Umn. No. It told you it was making that inference since it didn't know the table schema.
Otherwise it was exactly right about the problem.
It's partially right but led OP down the wrong lines of thinking because it interpreted the prompt as a date field being missing rather than the field named date being missing.
Tbh I don't blame it too much here as there is kind of a base level of understanding requred to use it successfully.
No. In what way is "If you have a column named foo add it to your query" wrong?