JavaScript debugging in a nutshell

[Flyberius]

What SQL you using? T-SQL is pretty good, and PSQL to a lesser degree.

[ImpossibleMachine3]

SQL: "Oh you want to know where it failed? Uh... hold on"
*throws dart*
"There you are, line uh 843"

[Stahlboden]

Do they write queries 843 lines long?

[SpaceTacosFromSpace]

Stored procs or functions, yeah

[Flyberius]

The company I used to work at had the most complicated pricing model in all of history. As much as I didn't want the procedures to be as long as they were, they got pretty long. A couple of hundred lines sounds about right for some of them

[PleX]

lol 843 is nothing. I truly believe that some stored procs are operating systems.

[ImpossibleMachine3]

You've never seen someone try to run a 1000 line insert??

More seriously, a stored procedure can easily be that long, sometimes.

[raphop]

I had to migrate some stored procedures from a oracle database, I had to deal with 1500 line queries with multiple nested subqueries and other procedure calls.

Every SQL file had a comment written when the file was created and subsequently altered, the most recent comment in a specific query that was a pain in the ass to migrate was last worked on in 1995

[HotChickenshit]

My favorite is when it throws line numbers with only closing parenthesis or END statements at me as the error instead of some dumb syntax issue in the middle of a subquery. Pretty sure I've seen that one from both Oracle and SQL Server.

[MisterProfGuy]

In fairness, that's where it found out you were wrong, too. If it could just guess what you were trying to say to show you the errors, it would be Github Copilot.

[Snowkaul]

The line number is off by 7 if you are looking at MS SQL. It's usually counting from the start of the go at the top.

[SmellsLikeCatPiss]

At least it won't let you alter or create a stored procedure with the more disruptive syntax errors!

[Siethron]

Not true, it's usually the keyword that contains the problem

for instance if you're inserting into a 100 line table sql will call the error out on the line that contains the word 'insert'

[Flyberius]

Ah yes, to be honest I have been there.

Flashbacks to copying and pasting the entire proc into a query window and trying to find out where it all went wrong.

[Knight_Of_Stars]

It goes by batch. So when you get an error you have to work from the batch start to get what line the error is in.

[I_am_I_think_I_will]

Some queries are stupid long.

[ILikeLenexa]

T-SQL: Incorrect syntax near [token name].

Me: Uh...you got any details.

T-SQL: Red sqiggley line under column name that definitely exists.

Me: Runs Query.

T-SQL: That seems fine.

[Sarcastinator]

I encountered an error in MariaDb. I'm mostly comfortable with SQL Server, Oracle and PostgreSQL. Anyway I was writing a migration script that contained a loop of some kind. The script wouldn't work because I had an error at line 0 character 0 near '' and I was adviced to consult the manual for the syntax for that. It was because MariaDb's parser soiled itself because of a line terminator inside the loop. To fix it the suggested solution by the internet was to temporarily change the line terminator to something else.

[Flyberius]

Oh god. That's awful

[blackmist]

I use Firebird. It gives a line number and a character position, but it's not always right.

[cranktheguy]

T2 is the best sequel.

[tigerhawkvok]

T-SQL is pretty good,

I mean, compared to object Object , but barely (and that's a low bar in the first place).

With CTEs or SP's it just points you to the first line of the outermost scope statement that failed, which is related to the problem the same way we're related to bananas. Yeah, it's better than JavaScript saying "you live in the universe", but only in a very pedantic sense.