Exception is printed even when exception is caught

So I have a table called User, with it's name column having an UNIQUE-constraint in the database, which defined in the model using .uniqueIndex() method.
You would expect that when I insert an user with a name which already exists like this:
```
addedUser = transaction {
createdUser = transaction {
User {
name = "Someone"
age = 9
}

}
```
, this would result in an exception being raised, like this:
```
org.jetbrains.exposed.exceptions.ExposedSQLException: java.sql.BatchUpdateException: Duplicate entry 'Someone' for key 'Name_UNIQUE'
```

But, when I put a try-catch clause around it like this:

```
try {
createdUser = transaction {
User {
name = "Someone"
age = 9
}
}
}catch (ex : ExposedSQLException){ //Or any other exception instead of ExcposedSQLException, even ex : Exception
println("Caught.")
}
```

, it still prints out this:

```
org.jetbrains.exposed.exceptions.ExposedSQLException: java.sql.BatchUpdateException: Duplicate entry 'Someone' for key 'Name_UNIQUE'
```

My question is: Why does it still print all this rubbish in the console, even though the exception is caught? When I debug and place an breakpoint on the catch clause, the code stops at the breakpoint, which implies the exception has been caught. Still, it prints the whole stacktrace.

I have a feeling it is due to the fact the code snippet which inserts into the database is being invoked by a `suspend fun someFuntion` , but I am not sure.