mirror of
https://github.com/FerretDB/documentdb.git
synced 2026-11-06 19:12:50 -05:00
Parag Jain
60dc82a14c
### Does this PR have any customer impact? ### Type (Feature, Refactoring, Bugfix, DevOps, Testing, Perf, etc) ### Does it involve schema level changes? (Table, Column, Index, UDF, etc level changes) ### Are you introducing any new config? If yes, do you have tests with and without them being set? ### ChangeLog (Refer [Template](../oss/CHANGELOG.md)) ### Description Fixing collection/empty API for new tables which has 3 columns only.
30 lines
1.3 KiB
PL/PgSQL
30 lines
1.3 KiB
PL/PgSQL
/*
|
|
* This function returns rows from an empty table that mimics a documentdb collection data table
|
|
* w.r.t. the data types of the columns.
|
|
*
|
|
* We need this to enable scenarios that require us to return an the equvalent of a
|
|
empty collection when the collection does not exists.
|
|
*
|
|
* The planner hook for __API_SCHEMA__.collection('db', 'collName') will call this function
|
|
* when the desired collection is not found.
|
|
*
|
|
* We could have made a similar change in the __API_SCHEMA__.collection() function itself,
|
|
* but having a different function provides better debuggability, i.e., the EXPLAIN will
|
|
* show "Function Scan on empty_data_table collection" instead of "Function Scan on collection".
|
|
* The latter could happen for other reasons.
|
|
*/
|
|
DROP FUNCTION IF EXISTS __API_SCHEMA_INTERNAL_V2__.empty_data_table;
|
|
CREATE OR REPLACE FUNCTION __API_SCHEMA_INTERNAL_V2__.empty_data_table(
|
|
OUT shard_key_value bigint,
|
|
OUT object_id __CORE_SCHEMA_V2__.bson,
|
|
OUT document __CORE_SCHEMA_V2__.bson)
|
|
RETURNS SETOF record
|
|
AS $fn$
|
|
BEGIN
|
|
RETURN QUERY EXECUTE format($$SELECT 0::bigint, null::__CORE_SCHEMA_V2__.bson, null::__CORE_SCHEMA_V2__.bson WHERE false$$);
|
|
END;
|
|
$fn$ LANGUAGE plpgsql;
|
|
COMMENT ON FUNCTION __API_SCHEMA_INTERNAL_V2__.empty_data_table()
|
|
IS 'mimics a data collection with 0 rows';
|
|
|