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.

  • Redacted@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 months ago

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

    • Strider@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      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.

    • 4am@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

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