lateral

问题 I have two different structured json files being piped in from a snowpipe. The only difference is that instead of a nested dict it has many nested arrays. I am trying to figure out how to transform structure 1 into one finalized table. I've successfully transformed structure 2 into a table and included the code below. I know I need to be making use of lateral flatten but have not been successful. **Structure 1: Nested Arrays (Need help on)** This json lives within a table and in column *

问题 I have a function called generate_table, that takes 2 input parameters ( rundate::date and branch::varchar ) Now I am trying to work on a second function, using PLPGSQL, that will get a list of all branches and the newest date for each branch and pass this as a parameter to the generate_table function. The query that I have is this: select max(rundate) as rundate, branch from t_index_of_imported_files group by branch and it results on this: rundate;branch 2014-03-13;branch1 2014-03-12;branch2

问题 I have a function called generate_table, that takes 2 input parameters ( rundate::date and branch::varchar ) Now I am trying to work on a second function, using PLPGSQL, that will get a list of all branches and the newest date for each branch and pass this as a parameter to the generate_table function. The query that I have is this: select max(rundate) as rundate, branch from t_index_of_imported_files group by branch and it results on this: rundate;branch 2014-03-13;branch1 2014-03-12;branch2

问题 I have the following query: query = "SELECT data #>> '{id}' AS id, data #>> '{name}' AS name, data #>> '{curator}' AS curator, data #> '{$isValid}' AS \"$isValid\", data #> '{customer}' AS customer, data #> '{$createdTS}' AS \"$createdTS\", data #> '{$updatedTS}' AS \"$updatedTS\", data #> '{$isComplete}' AS \"$isComplete\", (count(keys))::numeric as \"numProducts\", created_at FROM appointment_intakes, LATERAL jsonb_object_keys(data #> '{products}') keys INNER JOIN appointment_intake_users

问题 I am faced with a query similar to this: SELECT * FROM invoicable_interval i, LATERAL partition_into_months(i.start_date, i.stop_or_current_date) p; ... where partition_into_months is defined similar to this: CREATE FUNCTION partition_into_months(start_date DATE, stop_date DATE) RETURNS TABLE (start_date DATE, stop_date DATE, days INT) AS $$ ... $$ LANGUAGE sql IMMUTABLE; So I am doing a cross join with a variable interval for the secondary table, hence the (redundant) keyword LATERAL. This

问题 I am faced with a query similar to this: SELECT * FROM invoicable_interval i, LATERAL partition_into_months(i.start_date, i.stop_or_current_date) p; ... where partition_into_months is defined similar to this: CREATE FUNCTION partition_into_months(start_date DATE, stop_date DATE) RETURNS TABLE (start_date DATE, stop_date DATE, days INT) AS $$ ... $$ LANGUAGE sql IMMUTABLE; So I am doing a cross join with a variable interval for the secondary table, hence the (redundant) keyword LATERAL. This

问题 I am faced with a query similar to this: SELECT * FROM invoicable_interval i, LATERAL partition_into_months(i.start_date, i.stop_or_current_date) p; ... where partition_into_months is defined similar to this: CREATE FUNCTION partition_into_months(start_date DATE, stop_date DATE) RETURNS TABLE (start_date DATE, stop_date DATE, days INT) AS $$ ... $$ LANGUAGE sql IMMUTABLE; So I am doing a cross join with a variable interval for the secondary table, hence the (redundant) keyword LATERAL. This

问题 I'm running PostgreSQL 9.2.1 and have a plpgsql function that returns 3 columns. It's called like this (simplified): SELECT (my_function(b.input)).*, a.other, b.columns FROM table_a a JOIN table_b b ON a.id = b.id WHERE ... The function prints out a WARNING message and I was surprised to find it printed 3 times. It looks like the function gets called 3 times - presumably once for each column. This can't be good for performance! How can I make sure it's called only once? It's already marked

问题 DROP SCHEMA tmp CASCADE; CREATE SCHEMA tmp ; SET search_path=tmp; CREATE TABLE primes ( pos SERIAL NOT NULL PRIMARY KEY , val INTEGER NOT NULL , CONSTRAINT primes_alt UNIQUE (val) ); CREATE FUNCTION is_prime(_val INTEGER) RETURNS BOOLEAN AS $func$ DECLARE ret BOOLEAN ; BEGIN SELECT False INTO ret WHERE EXISTS (SELECT * FROM primes ex WHERE ex.val = $1 OR ( (ex.val * ex.val) <= $1 AND ($1 % ex.val) = 0 ) ); RETURN COALESCE(ret, True); END; $func$ LANGUAGE plpgsql STABLE; CREATE VIEW vw_prime

问题 Given a table defined as such: CREATE TABLE test_values(name TEXT, values INTEGER[]); ...and the following values: | name | values | +-------+---------+ | hello | {1,2,3} | | world | {4,5,6} | I'm trying to find a query which will return: | name | value | +-------+-------+ | hello | 1 | | hello | 2 | | hello | 3 | | world | 4 | | world | 5 | | world | 6 | I've reviewed the upstream documentation on accessing arrays, and tried to think about what a solution using the unnest() function would