[DERBY-6732] Enhance the foreignViews optional tool so that it can just create views on a single foreign schema

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.12.1.1
• Component/s: Tools
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 09/Sep/14 18:14
• Updated: 09/Sep/14 18:16

Description

Right now, the foreignViews optional tool creates views on all of the user tables in a foreign database. Sometimes all you want is one or two schemas. The bulk creation of views can also fail for databases which have weird, non-ANSI/ISO tables. We could add another trailing argument to the tool which limits view creation to a single schema. Something like this:

-- register like this
call syscs_util.syscs_register_tool
(
  'foreignViews',
  true,
  'foreignDatabaseURL',
  'XYZ_',    -- the prefix added to the local (Derby) schema names
  'foreignSchemaName'
 )

and

-- unregister like this
call syscs_util.syscs_register_tool
(
  'foreignViews',
  false,
  'foreignDatabaseURL',
  'XYZ_',    // the prefix added to the local (Derby) schema names
  'foreignSchemaName'
 )

Issue Links

• relates to: DERBY-4962 Create a table function which efficiently migrates data out of foreign databases and which can be used for ongoing data integration