Package FairCom.CtreeDb.Types

Class BINARY_FLAG

Object
BINARY_FLAG
public class BINARY_FLAG extends Object
Begin mode to be used on a CTField.SetFieldBinaryFlag(int) or a CTTable.SetBinaryFlag(int, int) call

  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    static final int
    BINARY_BLOB
    BLOB field created by c-treeSQL in v10
    static final int
    BINARY_CLOB
    CLOB field created by c-treeSQL in v10
    static final int
    BINARY_FIXED
    Table created by c-treeDB with v9 and after; CT_ARRAY and CT_2STRING fields are handled correctly
    static final int
    BINARY_MAX
    Largest Enum value
    static final int
    BINARY_UNKNOWN
    Table created by c-treeDB prior to v9 it indicates that CT_ARRAY or CT_2STRING field may or may not have extra 4 bytes at the beginning of data
    static final int
    BINARY_VARCHAR
    VARCHAR/LVARCHAR field created by c-treeSQL in v10
    static final int
    BINARY_WITH_LENGTH
    Table created prior to v9; but table was operated only with c-treeACE SQL and CT_ARRAY and CT_2STRING fields have four bytes at the beginning of the data resource was updated by utility
    static final int
    BINARY_WITHOUT_LENGTH
    Table created by c-treeDB prior to v9 but utility has updated this resource following types are handled correctly (as BINARY_FIXED) but used to indicate SQL types sharing CT_2STRING/CT_4STRING c-tree type other than varbinary/lvarbinary

  • Constructor Summary

    Constructors
    Constructor
    Description
    BINARY_FLAG()
     

  • Method Summary

    Methods inherited from class Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

  • Field Details

    • BINARY_UNKNOWN

      public static final int BINARY_UNKNOWN
      Table created by c-treeDB prior to v9 it indicates that CT_ARRAY or CT_2STRING field may or may not have extra 4 bytes at the beginning of data
      See Also:

    • BINARY_FIXED

      public static final int BINARY_FIXED
      Table created by c-treeDB with v9 and after; CT_ARRAY and CT_2STRING fields are handled correctly
      See Also:

    • BINARY_WITH_LENGTH

      public static final int BINARY_WITH_LENGTH
      Table created prior to v9; but table was operated only with c-treeACE SQL and CT_ARRAY and CT_2STRING fields have four bytes at the beginning of the data resource was updated by utility
      See Also:

    • BINARY_WITHOUT_LENGTH

      public static final int BINARY_WITHOUT_LENGTH
      Table created by c-treeDB prior to v9 but utility has updated this resource following types are handled correctly (as BINARY_FIXED) but used to indicate SQL types sharing CT_2STRING/CT_4STRING c-tree type other than varbinary/lvarbinary
      See Also:

    • BINARY_VARCHAR

      public static final int BINARY_VARCHAR
      VARCHAR/LVARCHAR field created by c-treeSQL in v10
      See Also:

    • BINARY_CLOB

      public static final int BINARY_CLOB
      CLOB field created by c-treeSQL in v10
      See Also:

    • BINARY_BLOB

      public static final int BINARY_BLOB
      BLOB field created by c-treeSQL in v10
      See Also:

    • BINARY_MAX

      public static final int BINARY_MAX
      Largest Enum value
      See Also:

  • Constructor Details

    • BINARY_FLAG

      public BINARY_FLAG()