Open Source RDBMS - Seamless, Scalable, Stable and Free

English | Login |Register

(click on this box to dismiss)

How to interpret the differences between these two manual pages?

I have mostly based jOOQ's CUBRID data type support to what is available here:

Unfortunately, that was not the best choice for the jOOQ source code generator, as it is reading db_attribute, which returns data types as defined here:

There is some confusion about a couple of data types. How to interpret this?

  1. The OBJECT, OID types aren't listed in the "Data Types" page
  2. What is the "_db_attribute" ELO type?
  3. "Data Types" mentions a "BIT VARYING" type, but "_db_attribute" returns "VARBIT". Is this a synonym?
  4. "Data Types" mentions various synonyms for what seems to be the SQL standard "NVARCHAR". "NVARCHAR", however, doesn't seem to exist, but "_db_attribute" returns "VARNCHAR" instead. Which synonyms work?

In the cases where there is confusion, I'm also interested in which type/name I should use when casting

링크 댓글 쓰기 (0) 선택된 답변
질문시간 2년 전
11 답변들
  • OID type is not documented since it's not an actual type, the correct type would be OBJECT but this also is not an actual type. OBJECT type is used when you're defining a column type as being a class type.
  • ELO type has been replaced by BLOB and CLOB. It is there only for historical reasons.
  • VARBIT is a synonym for BIT VARYING. The SQL syntax in CUBRID only understands BIT VARYING (this is what you should use for CAST).
  • NCHAR VARYING is the supported name for VARNCHAR/NVARCHAR type in CUBRID SQL syntax.
링크 댓글 쓰기 (2)
답변시간 2년 전

You are either using a very old browser or a browser that is not supported.
In order to browse you need to have one of the following browsers:

Internet Explorer: Mozilla Firefox: Google Chrome: