SQL/DDL Implementation › Extended SQL Naming › SQL Name Conflicts

SQL Name Conflicts

When you use extended SQL naming, it is possible for two or more file or field names to resolve to the same SQL name. Such name conflicts are not automatically resolved; it is your responsibility to ensure that name conflicts do not occur. Two ways name conflicts can occur are:

• Model names contain special characters.

  For example, two fields named "< start’" and "> start’" both resolve to the SQL name "_START’."

• The YSQLLEN model value contains a value less than 25.

  For example, if YSQLLEN is 24, two fields named "is a very long name1’" and "is a very long name2’" both resolve to the SQL name "_IS_A_VERY_LONG_NAME’."