Repository navigation
v0.0.3
Fixes
CONNECT BYonNUMBER(p)-typed key columns now translates. The
CONNECT BY→WITH RECURSIVElowering carries an ancestor-id path array for
cycle detection; the non-recursive arm kept the key column's typmod
(numeric(4,0)[]) while the recursive arm producednumeric[], and
PostgreSQL rejects a recursive union whose arms disagree on type. Any
hierarchy keyed on a precision-qualifiedNUMBER— i.e. most real Oracle
HR/ERP schemas — failed with
recursive query "__cb" column N has type numeric(4,0)[] .... Path-array
elements are now normalised totextin both arms. (5ba1bba)
Benchmarks
bench/run.shnow runs entirely in Docker on one bridge network (client,
Oracle XE, PostgreSQL, pgSaci), pgSaci from the published image, both engines
at 2 CPU / 2.5 GiB with Oracle spending its full 2 GiB licence and PostgreSQL
tuned to the envelope. Refreshed numbers in the README and docs. (f50f426)
Docker
docker pull levyks/pgsaci:0.0.3 — digest sha256:1217905bd2aa…, 9.77 MB
(static musl on scratch).