Changeset: a4c9d26a98b6 for MonetDB URL: https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a4c9d26a98b6 Added Files: sql/ChangeLog.scoping2 Branch: scoping2 Log Message:
Added ChangeLog for scoping2 branch. diffs (32 lines): diff --git a/sql/ChangeLog.scoping2 b/sql/ChangeLog.scoping2 new file mode 100644 --- /dev/null +++ b/sql/ChangeLog.scoping2 @@ -0,0 +1,27 @@ +# ChangeLog file for sql +# This file is updated with Maddlog + +* Mon Nov 30 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> +- Added 'schema path' property to user, specifying a list of schemas + to be search on to find SQL objects such as tables and + functions. The scoping rules have been updated to support this feature + and now it follows this order to find a SQL object: + 1. On occasions with multiple tables (e.g. add foreign key constraint, + add table to a merge table), the child will be searched on the + parent's schema. + 2. For tables only, declared tables on the stack. + 3. 'tmp' schema if not listed on the 'schema path'. + 4. Session's current schema. + 5. Each schema from the 'schema path' in order. + 6. 'sys' schema if not listed on the 'schema path'. + Whenever the full path is specified, ie "schema"."object", no search will + be made besides on the explicit schema. +- To update the schema path ALTER USER x SCHEMA PATH y; statement was added. + [SCHEMA PATH string] syntax was added to the CREATE USER statement. + The schema path must be a single string where each schema must be between + double quotes and separated with a single comma, e.g. '"sch1","sch2"' + For every created user, if the schema path is not given, '"sys"' will be + the default schema path. +- Changes in the schema path won't be reflected on currently connected users, + therefore they have to re-connect to see the change. Non existent schemas + on the path will be ignored. _______________________________________________ checkin-list mailing list checkin-list@monetdb.org https://www.monetdb.org/mailman/listinfo/checkin-list
