Programming

17392 readers

149 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

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 1 year ago

MODERATORS

[email protected]

136

The experience that made me hate programming, but that's all on me (lemmy.ml)

submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]

116 comments fedilink hide all child comments

Title before edit: I hate programming, why did i choose this field

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 8 points 5 months ago* (last edited 5 months ago) (3 children)

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".

[–] [email protected] 0 points 5 months ago (1 children)

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.

[–] [email protected] 3 points 5 months ago (2 children)

It made an incorrect inference, imagine how wrong it is on more complex questions.

[–] [email protected] 0 points 5 months ago* (last edited 5 months ago) (1 children)

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.

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago) (1 children)

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.

[–] [email protected] 0 points 5 months ago

No. In what way is "If you have a column named foo add it to your query" wrong?

[–] [email protected] 2 points 5 months ago

Of course. I would not recommend using it.

More like giving hints or a rough frame to work with.

[–] [email protected] 2 points 5 months ago (1 children)

ChatGPT rightly assumed you wouldn’t use a reserved word in your schema

[–] [email protected] 2 points 5 months ago

Perhaps, but we don't know and therein lies the problem.

[–] [email protected] 4 points 5 months ago

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.