postgres aggregate join matches to multiple array fields while creating views










0















I have the following schema + data:



create table org_users (
id character varying (255),
settings_id character varying (255) -- fk: settings.id
);

create table settings (
id character varying (255), -- primary key settings_id
perdiem_settings character varying (255), -- jsonised fk to perdiems.id
floor_settings character varying (255) -- jsonised fk to floors.id
);

create table perdiems (
id integer, -- primary key
name character varying(255)
);

create table floors (
id integer, -- primary key
name character varying (255)
);

insert into perdiems (id, name) values (1, 'perdiem 1');
insert into perdiems (id, name) values (2, 'perdiem 2');
insert into perdiems (id, name) values (3, 'perdiem 3');

insert into floors (id, name) values (1, 'floor 1');
insert into floors (id, name) values (2, 'floor 2');
insert into floors (id, name) values (3, 'floor 3');

insert into settings (id, perdiem_settings, floor_settings) values ('setting1', '"allowed_per_diem_ids":[1, 2]', '"allowed_floor_ids":[1]');
insert into settings (id, perdiem_settings, floor_settings) values ('setting2', '"allowed_per_diem_ids":[2, 3]', '"allowed_floor_ids":[1, 2]');
insert into settings (id, perdiem_settings, floor_settings) values ('setting3', '"allowed_per_diem_ids":[3, 1]', '"allowed_floor_ids":[1, 2, 3]');

insert into org_users (id, settings_id) values ('user1', 'setting1');
insert into org_users (id, settings_id) values ('user2', 'setting2');
insert into org_users (id, settings_id) values ('user3', 'setting3');


Now I want to create a view which will have aggregates from each of the other table, into an array field of its own. To explain with an example, the view that I want should be like:



org_user_id | settings_id | perdiems | floors
--------------------------------------------------------------------------------------------
user1 | setting1 | ['perdiem 1', 'perdiem 2'] | ['floor 1']
user2 | setting2 | ['perdiem 2', 'perdiem 3'] | ['floor 1', 'floor 2']
user3 | setting3 | ['perdiem 3', 'perdiem 1'] | ['floor 1', 'floor 2', 'floor 3']


This question is somewhat related to postgres aggregate join matches to an array field which deals with creating array fields out of join matches. However, here I want to create multiple array fields in a single view and so using a GROUP BY clause will not be feasible iiuc.



The query that I tried is:



CREATE OR REPLACE VIEW users_settings_view AS
SELECT ou.id AS org_user_id, <other fields...>
FROM org_users ou
LEFT JOIN settings pdr_s ON pdr_s.id = ou.settings_id
LEFT JOIN perdiems pdr ON pdr.id = ANY (SELECT json_array_elements(perdiem_settings::JSON->'allowed_per_diem_ids')::text::int FROM settings)


which creates duplicate records for each of the matching perdiem because of the join and not creating an array. Even if I crate an array as mentioned in the other stackoverflow question, it won't work if I have multiple string arrays as part of the view for different columns. Any way I can get multiple join matches to multiple array fields in a single view ?










share|improve this question




























    0















    I have the following schema + data:



    create table org_users (
    id character varying (255),
    settings_id character varying (255) -- fk: settings.id
    );

    create table settings (
    id character varying (255), -- primary key settings_id
    perdiem_settings character varying (255), -- jsonised fk to perdiems.id
    floor_settings character varying (255) -- jsonised fk to floors.id
    );

    create table perdiems (
    id integer, -- primary key
    name character varying(255)
    );

    create table floors (
    id integer, -- primary key
    name character varying (255)
    );

    insert into perdiems (id, name) values (1, 'perdiem 1');
    insert into perdiems (id, name) values (2, 'perdiem 2');
    insert into perdiems (id, name) values (3, 'perdiem 3');

    insert into floors (id, name) values (1, 'floor 1');
    insert into floors (id, name) values (2, 'floor 2');
    insert into floors (id, name) values (3, 'floor 3');

    insert into settings (id, perdiem_settings, floor_settings) values ('setting1', '"allowed_per_diem_ids":[1, 2]', '"allowed_floor_ids":[1]');
    insert into settings (id, perdiem_settings, floor_settings) values ('setting2', '"allowed_per_diem_ids":[2, 3]', '"allowed_floor_ids":[1, 2]');
    insert into settings (id, perdiem_settings, floor_settings) values ('setting3', '"allowed_per_diem_ids":[3, 1]', '"allowed_floor_ids":[1, 2, 3]');

    insert into org_users (id, settings_id) values ('user1', 'setting1');
    insert into org_users (id, settings_id) values ('user2', 'setting2');
    insert into org_users (id, settings_id) values ('user3', 'setting3');


    Now I want to create a view which will have aggregates from each of the other table, into an array field of its own. To explain with an example, the view that I want should be like:



    org_user_id | settings_id | perdiems | floors
    --------------------------------------------------------------------------------------------
    user1 | setting1 | ['perdiem 1', 'perdiem 2'] | ['floor 1']
    user2 | setting2 | ['perdiem 2', 'perdiem 3'] | ['floor 1', 'floor 2']
    user3 | setting3 | ['perdiem 3', 'perdiem 1'] | ['floor 1', 'floor 2', 'floor 3']


    This question is somewhat related to postgres aggregate join matches to an array field which deals with creating array fields out of join matches. However, here I want to create multiple array fields in a single view and so using a GROUP BY clause will not be feasible iiuc.



    The query that I tried is:



    CREATE OR REPLACE VIEW users_settings_view AS
    SELECT ou.id AS org_user_id, <other fields...>
    FROM org_users ou
    LEFT JOIN settings pdr_s ON pdr_s.id = ou.settings_id
    LEFT JOIN perdiems pdr ON pdr.id = ANY (SELECT json_array_elements(perdiem_settings::JSON->'allowed_per_diem_ids')::text::int FROM settings)


    which creates duplicate records for each of the matching perdiem because of the join and not creating an array. Even if I crate an array as mentioned in the other stackoverflow question, it won't work if I have multiple string arrays as part of the view for different columns. Any way I can get multiple join matches to multiple array fields in a single view ?










    share|improve this question


























      0












      0








      0








      I have the following schema + data:



      create table org_users (
      id character varying (255),
      settings_id character varying (255) -- fk: settings.id
      );

      create table settings (
      id character varying (255), -- primary key settings_id
      perdiem_settings character varying (255), -- jsonised fk to perdiems.id
      floor_settings character varying (255) -- jsonised fk to floors.id
      );

      create table perdiems (
      id integer, -- primary key
      name character varying(255)
      );

      create table floors (
      id integer, -- primary key
      name character varying (255)
      );

      insert into perdiems (id, name) values (1, 'perdiem 1');
      insert into perdiems (id, name) values (2, 'perdiem 2');
      insert into perdiems (id, name) values (3, 'perdiem 3');

      insert into floors (id, name) values (1, 'floor 1');
      insert into floors (id, name) values (2, 'floor 2');
      insert into floors (id, name) values (3, 'floor 3');

      insert into settings (id, perdiem_settings, floor_settings) values ('setting1', '"allowed_per_diem_ids":[1, 2]', '"allowed_floor_ids":[1]');
      insert into settings (id, perdiem_settings, floor_settings) values ('setting2', '"allowed_per_diem_ids":[2, 3]', '"allowed_floor_ids":[1, 2]');
      insert into settings (id, perdiem_settings, floor_settings) values ('setting3', '"allowed_per_diem_ids":[3, 1]', '"allowed_floor_ids":[1, 2, 3]');

      insert into org_users (id, settings_id) values ('user1', 'setting1');
      insert into org_users (id, settings_id) values ('user2', 'setting2');
      insert into org_users (id, settings_id) values ('user3', 'setting3');


      Now I want to create a view which will have aggregates from each of the other table, into an array field of its own. To explain with an example, the view that I want should be like:



      org_user_id | settings_id | perdiems | floors
      --------------------------------------------------------------------------------------------
      user1 | setting1 | ['perdiem 1', 'perdiem 2'] | ['floor 1']
      user2 | setting2 | ['perdiem 2', 'perdiem 3'] | ['floor 1', 'floor 2']
      user3 | setting3 | ['perdiem 3', 'perdiem 1'] | ['floor 1', 'floor 2', 'floor 3']


      This question is somewhat related to postgres aggregate join matches to an array field which deals with creating array fields out of join matches. However, here I want to create multiple array fields in a single view and so using a GROUP BY clause will not be feasible iiuc.



      The query that I tried is:



      CREATE OR REPLACE VIEW users_settings_view AS
      SELECT ou.id AS org_user_id, <other fields...>
      FROM org_users ou
      LEFT JOIN settings pdr_s ON pdr_s.id = ou.settings_id
      LEFT JOIN perdiems pdr ON pdr.id = ANY (SELECT json_array_elements(perdiem_settings::JSON->'allowed_per_diem_ids')::text::int FROM settings)


      which creates duplicate records for each of the matching perdiem because of the join and not creating an array. Even if I crate an array as mentioned in the other stackoverflow question, it won't work if I have multiple string arrays as part of the view for different columns. Any way I can get multiple join matches to multiple array fields in a single view ?










      share|improve this question
















      I have the following schema + data:



      create table org_users (
      id character varying (255),
      settings_id character varying (255) -- fk: settings.id
      );

      create table settings (
      id character varying (255), -- primary key settings_id
      perdiem_settings character varying (255), -- jsonised fk to perdiems.id
      floor_settings character varying (255) -- jsonised fk to floors.id
      );

      create table perdiems (
      id integer, -- primary key
      name character varying(255)
      );

      create table floors (
      id integer, -- primary key
      name character varying (255)
      );

      insert into perdiems (id, name) values (1, 'perdiem 1');
      insert into perdiems (id, name) values (2, 'perdiem 2');
      insert into perdiems (id, name) values (3, 'perdiem 3');

      insert into floors (id, name) values (1, 'floor 1');
      insert into floors (id, name) values (2, 'floor 2');
      insert into floors (id, name) values (3, 'floor 3');

      insert into settings (id, perdiem_settings, floor_settings) values ('setting1', '"allowed_per_diem_ids":[1, 2]', '"allowed_floor_ids":[1]');
      insert into settings (id, perdiem_settings, floor_settings) values ('setting2', '"allowed_per_diem_ids":[2, 3]', '"allowed_floor_ids":[1, 2]');
      insert into settings (id, perdiem_settings, floor_settings) values ('setting3', '"allowed_per_diem_ids":[3, 1]', '"allowed_floor_ids":[1, 2, 3]');

      insert into org_users (id, settings_id) values ('user1', 'setting1');
      insert into org_users (id, settings_id) values ('user2', 'setting2');
      insert into org_users (id, settings_id) values ('user3', 'setting3');


      Now I want to create a view which will have aggregates from each of the other table, into an array field of its own. To explain with an example, the view that I want should be like:



      org_user_id | settings_id | perdiems | floors
      --------------------------------------------------------------------------------------------
      user1 | setting1 | ['perdiem 1', 'perdiem 2'] | ['floor 1']
      user2 | setting2 | ['perdiem 2', 'perdiem 3'] | ['floor 1', 'floor 2']
      user3 | setting3 | ['perdiem 3', 'perdiem 1'] | ['floor 1', 'floor 2', 'floor 3']


      This question is somewhat related to postgres aggregate join matches to an array field which deals with creating array fields out of join matches. However, here I want to create multiple array fields in a single view and so using a GROUP BY clause will not be feasible iiuc.



      The query that I tried is:



      CREATE OR REPLACE VIEW users_settings_view AS
      SELECT ou.id AS org_user_id, <other fields...>
      FROM org_users ou
      LEFT JOIN settings pdr_s ON pdr_s.id = ou.settings_id
      LEFT JOIN perdiems pdr ON pdr.id = ANY (SELECT json_array_elements(perdiem_settings::JSON->'allowed_per_diem_ids')::text::int FROM settings)


      which creates duplicate records for each of the matching perdiem because of the join and not creating an array. Even if I crate an array as mentioned in the other stackoverflow question, it won't work if I have multiple string arrays as part of the view for different columns. Any way I can get multiple join matches to multiple array fields in a single view ?







      sql arrays postgresql join






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 17:27







      Sankar

















      asked Nov 14 '18 at 17:04









      SankarSankar

      2,27283457




      2,27283457






















          1 Answer
          1






          active

          oldest

          votes


















          1














          This will give you the result.



          select ou.id, array_agg( DISTINCT pd.name ),
          array_agg( DISTINCT f.name )
          from org_users ou join settings s on ou.settings_id = s.id
          cross join lateral
          json_array_elements_text(((s.perdiem_settings)::json->'allowed_per_diem_ids')::json)
          as jp(perdiem) join
          perdiems pd
          on pd.id = jp.perdiem::int
          cross join lateral
          json_array_elements_text(((s.floor_settings)::json->'allowed_floor_ids')::json)
          as js(floor) join
          floors f
          on f.id = js.floor::int
          GROUP BY ou.id;


          Demo



          Edit



          For cases of NULL settings, you may use a separate UNION ALL



          select id , ARRAY[NULL] as perdiems ,ARRAY[NULL] as floors FROM org_users 
          WHERE settings_id IS NULL
          UNION ALL
          (
          -- The above query --
          ) ORDER BY id;


          Demo2






          share|improve this answer

























          • this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

            – Sankar
            Nov 15 '18 at 11:58











          • @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

            – Kaushik Nayak
            Nov 15 '18 at 12:04












          • +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

            – Sankar
            Nov 15 '18 at 12:42











          • @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

            – Kaushik Nayak
            Nov 15 '18 at 13:00











          • @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

            – Kaushik Nayak
            Nov 15 '18 at 14:50











          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305373%2fpostgres-aggregate-join-matches-to-multiple-array-fields-while-creating-views%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          This will give you the result.



          select ou.id, array_agg( DISTINCT pd.name ),
          array_agg( DISTINCT f.name )
          from org_users ou join settings s on ou.settings_id = s.id
          cross join lateral
          json_array_elements_text(((s.perdiem_settings)::json->'allowed_per_diem_ids')::json)
          as jp(perdiem) join
          perdiems pd
          on pd.id = jp.perdiem::int
          cross join lateral
          json_array_elements_text(((s.floor_settings)::json->'allowed_floor_ids')::json)
          as js(floor) join
          floors f
          on f.id = js.floor::int
          GROUP BY ou.id;


          Demo



          Edit



          For cases of NULL settings, you may use a separate UNION ALL



          select id , ARRAY[NULL] as perdiems ,ARRAY[NULL] as floors FROM org_users 
          WHERE settings_id IS NULL
          UNION ALL
          (
          -- The above query --
          ) ORDER BY id;


          Demo2






          share|improve this answer

























          • this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

            – Sankar
            Nov 15 '18 at 11:58











          • @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

            – Kaushik Nayak
            Nov 15 '18 at 12:04












          • +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

            – Sankar
            Nov 15 '18 at 12:42











          • @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

            – Kaushik Nayak
            Nov 15 '18 at 13:00











          • @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

            – Kaushik Nayak
            Nov 15 '18 at 14:50
















          1














          This will give you the result.



          select ou.id, array_agg( DISTINCT pd.name ),
          array_agg( DISTINCT f.name )
          from org_users ou join settings s on ou.settings_id = s.id
          cross join lateral
          json_array_elements_text(((s.perdiem_settings)::json->'allowed_per_diem_ids')::json)
          as jp(perdiem) join
          perdiems pd
          on pd.id = jp.perdiem::int
          cross join lateral
          json_array_elements_text(((s.floor_settings)::json->'allowed_floor_ids')::json)
          as js(floor) join
          floors f
          on f.id = js.floor::int
          GROUP BY ou.id;


          Demo



          Edit



          For cases of NULL settings, you may use a separate UNION ALL



          select id , ARRAY[NULL] as perdiems ,ARRAY[NULL] as floors FROM org_users 
          WHERE settings_id IS NULL
          UNION ALL
          (
          -- The above query --
          ) ORDER BY id;


          Demo2






          share|improve this answer

























          • this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

            – Sankar
            Nov 15 '18 at 11:58











          • @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

            – Kaushik Nayak
            Nov 15 '18 at 12:04












          • +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

            – Sankar
            Nov 15 '18 at 12:42











          • @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

            – Kaushik Nayak
            Nov 15 '18 at 13:00











          • @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

            – Kaushik Nayak
            Nov 15 '18 at 14:50














          1












          1








          1







          This will give you the result.



          select ou.id, array_agg( DISTINCT pd.name ),
          array_agg( DISTINCT f.name )
          from org_users ou join settings s on ou.settings_id = s.id
          cross join lateral
          json_array_elements_text(((s.perdiem_settings)::json->'allowed_per_diem_ids')::json)
          as jp(perdiem) join
          perdiems pd
          on pd.id = jp.perdiem::int
          cross join lateral
          json_array_elements_text(((s.floor_settings)::json->'allowed_floor_ids')::json)
          as js(floor) join
          floors f
          on f.id = js.floor::int
          GROUP BY ou.id;


          Demo



          Edit



          For cases of NULL settings, you may use a separate UNION ALL



          select id , ARRAY[NULL] as perdiems ,ARRAY[NULL] as floors FROM org_users 
          WHERE settings_id IS NULL
          UNION ALL
          (
          -- The above query --
          ) ORDER BY id;


          Demo2






          share|improve this answer















          This will give you the result.



          select ou.id, array_agg( DISTINCT pd.name ),
          array_agg( DISTINCT f.name )
          from org_users ou join settings s on ou.settings_id = s.id
          cross join lateral
          json_array_elements_text(((s.perdiem_settings)::json->'allowed_per_diem_ids')::json)
          as jp(perdiem) join
          perdiems pd
          on pd.id = jp.perdiem::int
          cross join lateral
          json_array_elements_text(((s.floor_settings)::json->'allowed_floor_ids')::json)
          as js(floor) join
          floors f
          on f.id = js.floor::int
          GROUP BY ou.id;


          Demo



          Edit



          For cases of NULL settings, you may use a separate UNION ALL



          select id , ARRAY[NULL] as perdiems ,ARRAY[NULL] as floors FROM org_users 
          WHERE settings_id IS NULL
          UNION ALL
          (
          -- The above query --
          ) ORDER BY id;


          Demo2







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 15 '18 at 16:54

























          answered Nov 15 '18 at 8:05









          Kaushik NayakKaushik Nayak

          19.3k41331




          19.3k41331












          • this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

            – Sankar
            Nov 15 '18 at 11:58











          • @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

            – Kaushik Nayak
            Nov 15 '18 at 12:04












          • +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

            – Sankar
            Nov 15 '18 at 12:42











          • @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

            – Kaushik Nayak
            Nov 15 '18 at 13:00











          • @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

            – Kaushik Nayak
            Nov 15 '18 at 14:50


















          • this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

            – Sankar
            Nov 15 '18 at 11:58











          • @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

            – Kaushik Nayak
            Nov 15 '18 at 12:04












          • +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

            – Sankar
            Nov 15 '18 at 12:42











          • @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

            – Kaushik Nayak
            Nov 15 '18 at 13:00











          • @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

            – Kaushik Nayak
            Nov 15 '18 at 14:50

















          this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

          – Sankar
          Nov 15 '18 at 11:58





          this works. However, this fails to execute when there are records with null values. A user could have null settings, A setting could be null for either perdiem or floor. For example: insert into org_users (id, settings_id) values ('user4', null) does not return the user4 in the final output.

          – Sankar
          Nov 15 '18 at 11:58













          @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

          – Kaushik Nayak
          Nov 15 '18 at 12:04






          @Sankar : you may use Left joins instead of inner join. I was just using your sample that's all.

          – Kaushik Nayak
          Nov 15 '18 at 12:04














          +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

          – Sankar
          Nov 15 '18 at 12:42





          +Kaushik : Even if I change the from org_users ou join settings s on to from org_users ou left join settings s on I am not able to see the user4. dbfiddle.uk/… is the url. Or do I misunderstand which join you refer to ?

          – Sankar
          Nov 15 '18 at 12:42













          @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

          – Kaushik Nayak
          Nov 15 '18 at 13:00





          @Sankar : it may require a null check. I'm responding from my app now, will take a look and edit a while later. you may try with some options though

          – Kaushik Nayak
          Nov 15 '18 at 13:00













          @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

          – Kaushik Nayak
          Nov 15 '18 at 14:50






          @Sankar : It seems a lot of changes would be required in the joins to handle the NULL case especially due to the fact that json also returns null. This may hamper the performance for large rows. So, I would suggest a simpler approach using UNION ALL See dbfiddle.uk/…

          – Kaushik Nayak
          Nov 15 '18 at 14:50




















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305373%2fpostgres-aggregate-join-matches-to-multiple-array-fields-while-creating-views%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          How to read a connectionString WITH PROVIDER in .NET Core?

          Museum of Modern and Contemporary Art of Trento and Rovereto

          In R, how to develop a multiplot heatmap.2 figure showing key labels successfully