PostgreSQLOidDataType should not fail if OID is not a LargeObject

[jeffjensen]

Migrated from SourceForge — Bugs #437
Originally reported by coiouhkc on 2021-01-11 14:03:12.547000
Priority: 5
Assigned to jeffjensen
SF status: pending
Votes: 1

See https://www.postgresql.org/docs/11/datatype-oid.html, OID data type is not necessarily referring to large object, therefore it's totally OK, if there is no LargeObject mapped to the numerical value, e.g. 'table'::regclass.
Currently PostgreSQLOidDataType would fail with smth. like org.dbunit.dataset.DataSetException: org.postgresql.util.PSQLException: ERROR: large object 16548 does not exist

---

jeffjensen — 2021-10-30 15:05:41.456000
Thanks for the report. Please create a merge request with a proposed fix and a test that shows the problem so it stays fixed.

[jeffjensen]

Confirmed still open. PostgreSQLOidDataType#getSqlValue has a commented-out attempt at swallowing this case, with an explicit note that doing so unconditionally would hide real errors — so this needs a real fix that distinguishes "not a large object" from other SQL failures (e.g. by inspecting the driver's SQLState) rather than a blanket catch. Leaving open.