Supported Java, IDL, and JDBC/SQL types  Requirements for in-memory stateful failover

Chapter 29: Configuring Persistence Mechanisms

Table schema for binary storage

When using the binary storage technique, the table used by the JdbcStorage and JdbcStorageRegNew components has the schema described in Table 29-3.

Table 29-3: Table schema for binary storage

Column

Data format

ps_key (primary key)

The table’s primary key. The column datatype is different for different component primary key types (that is, the IDL or Java type specified in the Primary Key field on the Persistence tab):

  • If the component has no primary key, ps_key must be variable-length binary, 16-byte maximum length.

  • If the component’s key is the IDL string type, ps_key must be variable length character, 255-character maximum length.

  • If the component uses any other primary key type, including java.lang.String, ps_key must be variable length binary, 255-byte maximum length.

This column cannot be null.

ps_size

Integer, cannot be null.

ps_bin1

Variable length binary, 255 bytes maximum length, can be null.

ps_bin2

Variable length binary, 255 bytes maximum length, can be null.

ps_bin3

Variable length binary, 255 bytes maximum length, can be null.

ps_bin4

Variable length binary, 255 bytes maximum length, can be null.

ps_data

Binary large object. This type must be functionally equivalent to a Sybase image type. The JDBC driver used by the specified connection cache must allow access to the ps_data column using the JDBC setBytes and getBytes methods.





Copyright © 2005. Sybase Inc. All rights reserved. Requirements for in-memory stateful failover