Use INT4 for tx_step_outputs.step_id, so it is 4 bytes on CockroachDB too

[marc-merino]

Knit Bundle

View bundle

This PR is part of Knit bundle use-int4-for-step-id-columns-on-cockroachdb.

See the other review objects in this bundle:

• py: Use INT4 for datasource_outputs.step_id, so it is 4 bytes on CockroachDB too dbos-transact-py#884
• ts: Use INT4 for transaction_completion.function_num, so it is 4 bytes on CockroachDB too dbos-transact-ts#1403
• golang: Use INT4 for notifications.consumed_by_function_id, so it is 4 bytes on CockroachDB too dbos-transact-golang#499
• java: Use INT4 for tx_step_outputs.step_id, so it is 4 bytes on CockroachDB too #611 (this PR)

Bundle id: use-int4-for-step-id-columns-on-cockroachdb
Bundle title: Use INT4 for step-ID columns on CockroachDB

Closes #609

tx_step_outputs.step_id was created as INT, which is 4 bytes on Postgres but 8 bytes (INT8) on CockroachDB. Every other step-ID column is INT4, and since the system database is shared across SDKs, a reader that decodes the column as a 32-bit integer fails on CockroachDB.

The TxStepSchema.createTable now creates it as INT4. That is a no-op on Postgres, and existing CockroachDB tables keep INT8 because the statement uses CREATE TABLE IF NOT EXISTS.

The same fix is proposed for the other DBOS SDKs.

Testing

• Ran the statement on CockroachDB: the column is now INT4 (it was INT8).
• The txstep tests pass.

[devhawk]

Thanks @marc-merino!

[marc-merino]

You're welcome, @devhawk :) I DM'd you on Discord about these PR's, would really appreciate it if you had a look. Cheers