Technology Editor : Language


This tab describes the languages implemented by the technology and allows overwriting any of the properties of the language.

Note concerning User Functions:

To make a user function available for a specific technology:


  1. In the Language column, select the language of the technology.
  2. Select Default.
  3. Make sure that you have selected the corresponding technology from the Technology type list on the Definition tab. The Oracle Data Integrator API does not work with user functions.

Language
Language that is totally or partially implemented by the technology, selected from the list of defined languages.

CompatibleShows that the language for the technology inherits all the language elements marked as standard. For more information, see the Language Editor topic.

DefaultShows that this is the default language for this technology.

Object Delimiter
Character used to delimit object names. Replaces the standard delimiter given in the language.
Caution: If the two delimiters (before and after the object name) are different, then you should use both of them. If not, one delimiter is enough.
Use a single double-quote " to generate code like this:
create table MySchema."My_Table" ( ...
Use two square brackets [] to generate code like this:
create table MySchema.[My_Table] ( ...


Word Separator 

Characters that can be used to separate language words (objects, key words, literals). The characters declared in this list cause the object (table/schema/column) to be enclosed in the characters declared for the 'Object Delimiter'. For example, if the table name contains a # character, some databases do not accept that table name to be used, except where enclosed in double quotes: MySchema.MyTable#1 becomes MySchema.'MyTable#1' if the ' (single quote) is declared as the object delimiter and # is declared as a word separator.

Literal Delimiter 

Character used to delimit the literal names (values). Replaces the standard delimiter given in the language.

Caution: If the two delimiters (before and after the literal) are different, then you should use both of them. If not, one delimiter is enough.


Objects case-sensitive 

Object names in this technology are case-sensitive.

For example, objects are not case-sensitive in the SQL Language by default. Therefore, code like this is generated to preserve names using upper and lowercase letters:
create table Snps_Temp.dbo.My_Table
  (
     My_Column1 VARCHAR(20) NULL,
     MY_COLUMN2 VARCHAR(20) NULL
   )

If Objects case-sensitive is selected, then code like the following is generated:
create table Snps_Temp.dbo."My_Table"
  (
    "My_Column1" VARCHAR(20) NULL,
     MY_COLUMN2 VARCHAR(20) NULL
   )


Words case-sensitive Keywords of this language are case-sensitive.

No comments:

Post a Comment