MrOzwaldManJun 11, 2024

I hate programming, why did I choose this field.

https://lemmy.ml/post/16742521

I hate programming, why did I choose this field. - Lemmy

TL;DR: Stupid mistake, made by hours waste. Basically, I was extracting date from the SQL db, and it was not displaying. I tried everything, heck I even went to chatgpt, and copilot. Two and half hours of trying every single thing under the sun, you know what was the issue? SELECT task, status, id FROM mainWorkSpace WHERE user_id = @user_id I FUCKING FORGOT TO ADD ‘date’ TO THE DAMN QUERY. TWO AND HALF HOURS. I was like, “Ain’t no way.” as I scrolled up to the query and there it was, a slap in the face, and you know what was the fix? SELECT task, status, date, id FROM mainWorkSpace WHERE user_id = @user_id Moral of the story, don’t become a programmer, become a professional cat herder instead.

Show threadStriderJun 11, 2024

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:

SELECT task, status, id, created_at FROM mainWorkSpace WHERE user_id = @user_id

This will include the created_at column in the output of your query.

🤷

Show threadRedactedJun 11, 2024

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:

Although I would question the sense in calling a date field "date".
Show threadatzanteolJun 11, 2024

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.

Show threadRedactedJun 11, 2024
It made an incorrect inference, imagine how wrong it is on more complex questions.
Show threadatzanteolJun 11, 2024

Umn. No. It told you it was making that inference since it didn’t know the table schema.

For example, if you have a column named “created_at” or “date” in your mainWorkSpace table, you can add it to your SELECT statement

Otherwise it was exactly right about the problem.

Show threadRedacted
So wrong then.
Jun 11, 2024 at 2:58pmWeb
Show threadatzanteolJun 11, 2024
No. In what way is “If you have a column named foo add it to your query” wrong?