fix: question mark for placeholder does not work

[vanvuongngo]

fix: question mark for placeholder does not work

If I follow the example with a question mark for a placeholder then this exception is thrown.

connection.execute("delete from tb_test where id=?", ['test3']);

"[object Object]" is not one of the cases of error

or this with a try-catch

error:

(new Error("[object Object] (see error.payload)", "dist.bindings.js", 157))

error.payload:

{ tag: "query-failed", val: "Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState(E42601), message: "syntax error at end of input", detail: None, hint: None, position: Some(Original(35)), where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("scan.l"), line: Some(1240), routine: Some("scanner_yyerror") }) }" }

environment

• spin: 3.0.0
• macos
• postgresql 17
• target: wasm32-wasip1

[vanvuongngo]

add try-catch to get error informations

[itowlson]

Thanks for flagging this! However, the page in question covers both MySQL and Postgres. The example in this PR is for MySQL, for which the question mark is correct. And we didn't want to clutter the page with MySQL and Postgres examples that were almost identical, so instead the paragraph above the sample links to a Postgres example.

I'll look at adding comments to the sample noting differences for Postgres.

@karthik2804 is it worth surfacing the error payload more visibly in this case, or is that part of the JS exception system and out of our control?