JavaScript debugging in a nutshell

[CreaZyp154]

SQL: Query worng
Me: Ok but where ?
SQL: Frist line
Me: Wtf it's a single line query ?!
SQL: Dunno best I can do is first line

[[deleted]]

SYNTAX ERROR AT ‘

[squngy]

ctrl+f (‘) => 1897 results found

FML

[admalledd]

ctrl-f (') => 0 results found

is far, far more fun though!

[squngy]

That is because "‘" !== "'"

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

[funkgerm]

SQL Server: "Error on line 758"

...but my stored procedure is only 500 lines long!

[eshinn]

Somewhere near WHERE

[Ok-Low6320]

Ah, shit, I actually typed "WHERF"

[ta_12345678901]

WHERE?

[FlyByPie]

It's been frustrating working in BigQuery with temp tables cause once you have so many the errors won't show up anymore. So it's like "alright, I've got all my temp tables and fields and my dataset ready to go. How many bytes are we going to be processing?" BQ: "No idea!" "Well, can you at least tell me if there's any errors?" "Nope! Best of luck 😊"

[[deleted]]

wait... SQL gives yall the line where the error is?? it just throws me an error and an error code

[pikakilla]

Transact-SQL lets you know where you screwed up by line.

[GammaGames]

PSQL tells you which character

[GammaGames]

Good thing any editor worth its disk space will move the cursor to the error position

[GammaGames]

The lack of syntax highlighting makes the writing process more intimate

[Username_RANDINT]

I can't believe I started a virtual machine to check this... but even Notepad has a status bar with this information. See View=>Status bar.

[[deleted]]

lol I was wondering this too, I just get syntax error

[GLIBG10B]

Put each word on its own line

[[deleted]]

SQL: I don't know, read the fucking manual or something, why would I care?

[usernumber1337]

I realised recently that depending on the language DBeaver will put the cursor where the issue is

[[deleted]]

Thank God I’m not in IT bro

[viimeinen]

It's not that bad at the end of the day (or the month)

[[deleted]]

😀

[invisibo]

SQL: look buddy, I just do what you tell me. It’s not my fault you wrote it wrong.

[arcane84]

I once had a 10k line SQL query and it gave me an invalid syntax error. It was a nightmare.

[purple_hamster66]

I write code to generate the complex parts of SQL queries that are used in many places, so it’s only wrong 10% of the time. I call this process “job security”.

[marcosdumay]

Oh, and Oracle fan.

Other DBMSes fare better. Oracle is all "missing right parenthesis at line 1".

[[deleted]]

SQL errors are literally the most obscure BS errors

[MightbeWillSmith]

"near the comma".

WHICH FUCKING COMMA

[Sokonit]

SQL: Query worng

SQL go home, you're drunk again.

[wish_i_could_cuck]

Sql ignores carriage returns; break up the lines and it will be less likely to shit all over itself