| Triggers created in different schema than table it references [message #25663] |
Fri, 19 January 2007 22:32 |
Eclipse User |
|
|
|
Originally posted by: francine.grimmer.ncr.com
When trying to 'Edit' a trigger that has been created in a different
schema than the table it references, a failure occurs when it tries to get
its source.
When loading the trigger from the database into the SQL Model object, it
is placed in the list of triggers hanging off the subject table. Thus the
trigger is displayed in the DSE via its subject table. If you right click
and choose the Edit option, the SQLTools will create a ProcIdentifier
object that contains a map with the OWNER (trigger's schema name),
TABLENAME (its subject table name), and NAME (trigger name). The SQLTools
createDBItem then calls the ModelUtil.findProceduralObject passing the
procIdentifier to locate the SQLObject from its procIdentifier. But the
findProceduralObject method tries to locate the trigger by looking in its
schema (OWNER) for the list of tables that match the trigger subject table
name. But because the subject table does not reside in the same schema as
the trigger, it fails and returns null.
One possibility is that the OWNER reflect the subject table schema instead
of the trigger schema. This appears to be in the DTP code and not
something we can code around. Can someone look at this and tell us how to
work around this problem? Or should I enter a bugzilla report?
thanks,
-francine
|
|
|
Powered by
FUDForum. Page generated in 0.03317 seconds
] 
Search
Help
Register
Login
Home
