Oracle support is broken

[stellerex]

Support for Oracle DB as a JDBC transaction log seems to be broken:

CREATE TABLE tx_events (
  event_offset BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
  event_key VARCHAR2(255),
  tx_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  topic VARCHAR2(255) NOT NULL,
  v BLOB NOT NULL,
  compacted INTEGER NOT NULL), Error Msg = ORA-30675: identity column must be a numeric type

If the table is created manually with event_offset being NUMBER instead of BIGINT, it still cannot be initialized:

SELECT event_offset, topic FROM tx_events WHERE event_offset < ? ORDER BY event_offset DESC LIMIT ?, Error Msg = ORA-00933: SQL command not properly ended

Since it is broken for more than a year, I wonder if anyone is using Oracle as a backend?

[refset]

Hi @stellerex we're not actively supporting any teams using the Oracle JDBC backend currently (transaction log or document store), but we can investigate what's happened and get this working again if it's important for you. Please get in touch if so: [email protected]

Part of the explanation for the drift here has been the challenge/inability of integrating Oracle into the CI checks due to the proprietary licensing and deployment hurdles. Apologies for the surprise and inconvenience caused.