Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Icetips Article
Back to article list
Search Articles
Add Comment
Printer friendly
Direct link
Par2: Oracle views and errorcode 47 2000-05-31 -- Bruce Wells Clarion ignores any fields in the Oracle table that are not defined in the
Clarion dictionary so it is not possible to get an error 47 by missing one
or more of the Oracle columns. However, all columns from the primary key
(on the Oracle side) must be in the Clarion dictionary and the Clarion
primary key fields must exactly match the Oracle primary key fields. If the
developer is allowing updating of the data files combined in the view,
Oracle only allows one of these tables to be updated. If this update is
allowed, all of the primary key columns, for the table to be updated, must
be in the Oracle view.
If there is a data type mismatch between Clarion and SQL that an error
47 will result. Therefore if, after the synchronization, the developer
changed the Clarion data types from the ones selected during the sync an
error 47 will occur.
The external name in the Clarion dictionary is only necessary if the
Clarion field name is changed. Our naming convention on the Oracle side is
set for the advantage of the DBAs so that all columns can be identified and
associated with a schema. We change this naming in Clarion to make the
program more readable. If we didn't do that the external name would not be
needed. This is another question to ask the developer.
Today is November 21, 2024, 7:46 am This article has been viewed 35315 times.
|
|