Lack of error codes and reliance on string-based custom errors

[i64]

The current exposed API of the kuzu needs to include error codes, which hinders effective error handling and logic development. Instead of returning standardized error codes, the library relies on custom error messages represented as strings. This introduces challenges when attempting to check and handle errors programmatically.

char *query = "MATCH (a:Person) WHERE a.isStudent = $1 RETURN COUNT(*)";
kuzu_prepared_statement *preparedStatement = kuzu_connection_prepare(connection, query);

kuzu_prepared_statement_bind_bool(preparedStatement, (char *)"1", true); 
// kuzu_connection_execute() succeeds

kuzu_prepared_statement_bind_int64(preparedStatement, (char *)"1", true); // typo on purpose
// $1 (bool:int64) causes kuzu_connection_execute() to fail, but we don't receive an error code. 
// Handling this error in logic becomes difficult due to the reliance on string-based error representation.

kuzu_prepared_statement_bind_bool(preparedStatement, (char *)"2", true); // typo on purpose
// $2 (undefined) causes kuzu_connection_execute() to fail, but we don't receive an error code. 
// Handling this error in logic becomes difficult due to the reliance on string-based error representation.