I don’t play this game and have no idea how I ended up here. But, I know the answer to this one, I think.

I once wanted to live in the desert. I worked for it for a whole year (when such was possible): saving, planning, changing vehicles, then job hunting. I totally got there.

After one week in the desert I decided I fucking hate it. For awhile I thought it was a total fucking loss. But, then I realized that if I’d not gone to the desert I’d never have learned I hated it. I’d still be unhappy and still wanting something that wasn’t going to work. I’m glad I went to the desert or I’d never have found my love of the mountains.

If it’s not a significant sacrifice to pay for a membership then buy the damned thing. See if it makes you happy. What is it, $10-20 for a month? And, that’d answer a question about happiness you’ve had for years. Seems cheap.

If that $10-20 is important, PM me. I’ll give it to you. Get your answer. I’d consider it money well spent.

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.

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.

If object definitions were replaced by table/query definitions in planning then you’d probably not have made the initial error. Again, it looks different. But, the concept is the same.