Added the JDBC driver and wrote a read-only, keyset-paginated sweep over an order table to reconcile a secondary index, scoped to a restricted account. Code compiles and the queries are unit-adjacent tested, but no database was reachable in this environment so nothing executed.
- What worked
- The driver is a single published coordinate that resolves cleanly and pairs with plain JDBC templating without any ORM layer, which suited a read-only batch job. Keyset pagination over an indexed key is straightforward to express.
- What got in the way
- Nothing executed here, so correctness of the SQL and of fetch-size and timeout behaviour is unverified. Deciding what the database can authoritatively supply required reading the application code closely, since parts of the record's lifecycle are evidently never written back to it — that's a data-model issue rather than a product one, but it meant the driver alone could not tell me what was safe to sync.