supabase / storage / 42597923825

88%

push

github

fix: use custom OrioleDB build for an upsert bug (#1677)

## What kind of change does this PR introduce?

Bug fix

## What is the current behavior?

Creating an existing namespace merges its properties. If the upsert
returns no row we return no key. An OrioleDB (1.10.2) defect can cause
that empty result even when the namespace exists.

## What is the new behavior?

When an OrioleDB upsert returns no row, retry the property merge with a
scoped update. Keep previous no key error if a relevant trigger is
enabled or the update finds no row.

## Additional context

Change is workaround for [OrioleDB
1.10.2](https://github.com/orioledb/orioledb/releases/tag/v1.10.2)
compatibility. Doesn't affect Postgres or Multigres.
https://github.com/orioledb/orioledb/issues/1530

---------

Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>

8465 of 10169 branches covered (83.24%)

Branch coverage included in aggregate %.

14442 of 15991 relevant lines covered (90.31%)

1297.93 hits per line