Implement replace on the Database Column

[wdanilo]

This task is automatically imported from the old Task Issue Board and it was originally created by James Dunkerley.
Original issue is here.

---

    replace : Text | Column -> Text | Column -> Case_Sensitivity -> Boolean -> Boolean -> Column
    replace self term="" new_text="" case_sensitivity=Case_Sensitivity.Sensitive only_first=False use_regex=False =

• Surfaces the same options as Text.replace.
• Should follow the same API as the in-memory version.
• Case Insensitive in non-default locale should be an error.
• What modes are available will depend on what is supported by the dialect.

This should be done by mapping the modes to specific dialect operators:

case_sensitive	use_regex	only_first	operation
True	False	True	Replace_First
True	False	All	Replace_All
False	False	True	IReplace_First
False	False	All	IReplace_All

etc.

[GregoryTravis]

Looking through the Postgres and SQLite docs, it looks like

case_sensitive	use_regex	only_first	postgres	sqlite
True	False	False	supported	supported
True	False	True	via regex(2)	via instr(3)
False	False	False	via regex(1)	unsupported
False	False	True	via regex(1,2)	via instr(3)

(1) Postgres regex supports case insensitivity; this would require escaping the search string so it would not act as a regex.
(2) Postgres regex supports only_first starting with version 13; this would require escaping the search string so it would not act as a regex.
(3) Use INSTR() to find the lowercased string, then replace it via concatenation

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-07):

Progress: Researched db implemenetations It should be finished by 2023-07-13.

Next Day: basic replace

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-11):

Progress: figuring out which flags are supported where; tests It should be finished by 2023-07-13.

Next Day: basic replace

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-11):

Progress: basic replace, and one other case It should be finished by 2023-07-13.

Next Day: more cases

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-12):

Progress: all cases and tests It should be finished by 2023-07-13.

Next Day: review

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2023-07-13):

Summary: There is 1 days delay in implementation of the Implement replace on the Database Column (#5160) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: use metadata

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-13):

Progress: using metadata to reduce cases It should be finished by 2023-07-14.

Next Day: try to use metadata

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2023-07-14):

Summary: There is 3 days delay in implementation of the Implement replace on the Database Column (#5160) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: postgres version in compatibility

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-14):

Progress: using metadata to reduce cases It should be finished by 2023-07-17.

Next Day: debug it

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2023-07-17):

Summary: There is 1 days delay in implementation of the Implement replace on the Database Column (#5160) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: review

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-17):

Progress: do supported check early It should be finished by 2023-07-18.

Next Day: debug it

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2023-07-18):

Summary: There is 1 days delay in implementation of the Implement replace on the Database Column (#5160) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: review

[enso-bot]

Greg Travis reports a new STANDUP for today (2023-07-18):

Progress: reivew; working on java round; debugging time zone test failures It should be finished by 2023-07-19.

Next Day: java round

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2023-07-19):

Summary: There is 1 days delay in implementation of the Implement replace on the Database Column (#5160) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: review; CI failures