This says that the current schema will be entered by hand in the text box below. This says that the current authorization ID should be used as the current schema. Radio buttons - Use authorization ID as current schema. This toggles the setting to omit / include the current schema in SQL generated by the SQL Query Builder. In the UI, the following controls will be used:Ĭheck-box - Omit current schema in generated SQL. They will be able toggle an Omit current schema from generated SQL setting, and they will be able to specify whether the curent Authorization ID should be used as the current schema or enter the current schema name by hand. To configure this option, the user will be able to set some preferences or properties. This page describes how this option might be configured in the UI through either preferences or properties and raises the question of what level is appropriate for setting these preferences or properties. If statements are moved to an environment which has a different current schema, then if tables are unqualified by the current schema, it may not be necessary to modify the statements. Omitting the current schema may simplify moving SQL statements from one environment to another.It can be used to enforce qualification / non-qualification of tables by the current schema.This option is useful for a number of reasons: For example, if the current schema is DBA and the table BOOKS belongs to this schema, then references to this table in SQL generated by the SQL Query Builder will be either BOOKS or DBA.BOOKS, depending on whether the user has chosen to omit the current schema or not. When this option is switched on, tables which belong to the current schema will be unqualified.
The SQL Query Builder will give the user the ability to omit the current schema in generated SQL. 3 Level at which the settings are configured.
0 kommentar(er)
