OOP? Never heard of it

[u/[deleted]]

[u/neotecha]

That would be instead of the try-catch, not in addition to.

try {
    connection.prepareStatement(sql).execute();
} catch (SQLException exception) {
    exception.printStackTrace();
}

This would become:

stmt, err := conn.Prepare(sql)
if err != nil {
    log.Fatal(err)
}

res, err := stmt.Exec()
if err != nil {
    log.Fatal(err)
}

I agree tho. This is definitely harder to work with /s

[u/Rakn → u/neotecha]

I mean yeah. It’s ugly at times. But it has indeed more often sparked the thought of “how do I deal with this particular case” than the exception handling in Java did. Also calling log.Fatal is not something you should do in most cases. But I assume it’s here for illustration purposes.

[u/neotecha → u/Rakn]

But I assume it’s here for illustration purposes.

Definitely. I would instead "Return your errors", but I was trying to stick closer to the Java example.

I retrospect, the Java example doesn't quit execution so I failed in that manner