this post was submitted on 11 Jun 2024
130 points (82.2% liked)
Programming
17661 readers
277 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
The reason the date is not in the output is because you didn't include a date column in your SELECT statement.
If you want to include the date in the output, you'll need to add a column that contains the date to your SELECT statement. For example, if you have a column named "created_at" or "date" in your mainWorkSpace table, you can add it to your SELECT statement like this:
This will include the created_at column in the output of your query.
🤷 Gpt, first try. I don't know what you asked.
Ah I see ChatGPT is being as accurate as ever making up a created_at field completely unprompted. They've already found the correct SQL:
SELECT task, status, id, date FROM mainWorkSpace WHERE user_id = @user_id
Although I would question the sense in calling a date field "date".
Well I have to defend it here, it explicitly stated
if you have a column named "created_at" or "date"
But yeah anyhow anyone should be able to figure the own solution out with this. Nonwithstanding that if you need gpt for this, you might not have a good time in general.
ChatGPT rightly assumed you wouldn’t use a reserved word in your schema
Perhaps, but we don't know and therein lies the problem.
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?
I pasted my code multiple times and didn't give me that answer. Maybe it's because you only copied the query and not the code that i wrote.
I also posed the question why I don't get a date in the output of course.
I was talking about this date which was used to display the date assigned by the user, but the column was not displaying with the date because I wasn't asking sql for the date (if you've looked at the query), so yeah, a stupid mistake caused for a stupid angry post.