Java exception when querying calculated field with divide by zero

[HenryNebula]

Description

When a JDBC driver throws an exception during data conversion (e.g., divide-by-zero in a calculated column), the Java exception propagates uncaught through fetchone() instead of being handled gracefully. Users expect None/null for errored columns rather than raw Java exceptions.

Steps to Reproduce

1. Connect to a database via JDBC using jaydebeapiarrow
2. Execute a query with a calculated column that may cause divide-by-zero (e.g., X/Y where Y=0)
3. Call fetchone() or fetchall()

Expected Behavior

The errored column should produce None, and the rest of the row should be returned normally.

Actual Behavior

A Java exception (e.g., com.filemaker.jdbc.FMSQLException) propagates up through fetchone(), causing the entire row to be lost.

Legacy Issue

baztian/jaydebeapi#58

[HenryNebula]

Triage fix: #83