For me it’s just the brain doing unnecessary calculations to see how this ui element was made. Why unnecessary? because when it calculates, it’s the time after work where it starts calculating, like brain, you’re tired, stop it.

It’s not you investigating, it’s just the brain calculating and coding how it was made in the language I learned.

Usually, it’s more sane to embed formatting in the string itself rather than having styling separately defined (i.e. CSS, kinda).

like this: <b>Bold Text</b>?

I posted the entire function where the issue was occuring and it was trying to solve the function and not the query.

Thanks for sharing your experience, who knew a frustrating post written by me would give me lessons which i am going to take to heart.

I would like mine blue with an army’s helmet.

Assuming you’re coming from a linear programming and OOP background, then data (incl. SQL) kinda sucks because it’s not always clear how to apply existing concepts. But, doing so is absolutely critical to success, perhaps more so than in most OOP environments. Your post isn’t funny to me because I’d be laughing at you, not with you.

That’s correct, I have done a lot of OOP in Java and C#, and the internship I’m doing is with C# and ASP.Net.

If a variable is fucked, the first questions you should answer are, “Where’d it come from?” and “What’s its value along the way?”. That looks a lot different in Python than SQL. But, the troubleshooting concept is the same.

You see, I wasn’t thinking clearly at the time, wasn’t looking at the right place, and like the post says, I’ve finally looked at the right place and made me feel frustrated. The frustration was at myself not at programming.

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.

This often happens when I’m tired or overworked. Maybe it’s because of this and the frustration of the situation that had me (idk the word) go angry and write this post.

Thanks will keep in mind next time it happens

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.

My second pair of eyes was in an another country for business stuff so I had to solve it all by myself and because of the frustration, i wrote this post. Sorry about that

Thanks for sharing that, I’ve learned my lesson from you and the others in the comments

Agreed. Sorry for my post, it was written in frustration of the situation

I know that, my anger has manifested this post, and I shouldn’t have criticized the entire field

The title was an over exaggeration on my part

it’s indeed a new language for me and I haven’t developed that ability to know where the bug is happening but I am going to get there.

In those kinds of situations you need to remember to try to break the problem down into simpler sections to identify where the problem lies.

Learned that the hard way.

One of the first steps would be to run SELECT * FROM mainWorkSpace WHERE user_id = @user_id and see if that returns anything.

It’s one of those situations where if i write something, i forget it because it is doing its thing and about selecting everything, i should’ve done that and it’s my mistake.

I meant like this: