On 2021-Oct-08, Matthias van de Meent wrote: > On Fri, 8 Oct 2021 at 11:47, Aleksander Alekseev > <aleksan...@timescale.com> wrote:
> > In order to do this, the SQL syntax should be modified. The proposed > > syntax is based on Matthias van de Meent's idea [6]: > > Seems fine > > > ``` > > CREATE TYPE <type-name> AS JSONB_DICTIONARY ( > > learn_by = { {"table_a", "column_a"}, {"table_b", "column_b"}, ... }, Actually, why is it a JSONB_DICTIONARY and not like CREATE TYPE name AS DICTIONARY ( base_type = JSONB, ... ); so that it is possible to use the infrastructure for other things? For example, perhaps PostGIS geometries could benefit from it -- or even text or xml columns. The pg_type entry would have to provide some support procedure that makes use of the dictionary in some way. This seems better than tying the SQL object to a specific type. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ #error "Operator lives in the wrong universe" ("Use of cookies in real-time system development", M. Gleixner, M. Mc Guire)