Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Git Pull Request:
https://github.com/infinispan/infinispan/pull/10810, https://github.com/infinispan/infinispan/pull/10811

For jdbc and sql cache-store, would be good if we have a list of which column types we should use to be compatible with infinispan, for example:

mysql and mariadb

id column type = VARCHAR(255)
data column type = VARBINARY(1000)
timestamp column type = BIGINT
segment column type = BIGINT

postgresql and postgresql plus

id column type = VARCHAR(255)
data column type = BYTEA
timestamp column type = BIGINT
segment column type = BIGINT

sql server

id column type = NVARCHAR(255)
timestamp column type = BIGINT
data column type = VARBINARY(1000)
segment column type = BIGINT

sybase

id column type = VARCHAR(255)
data column type = IMAGE
timestamp column type = BIGINT
segment column type = BIGINT

oracle

id column type = VARCHAR2(255)
timestamp column type = NUMBER
data column type = RAW(1000)
segment column type = NUMBER

is cloned by

JDG-5858 [Docs]Add a list of which column type we should use for the supported databases

relates to

ISPN-14441 string-keyed-jdbc-store should verify the TB-Table definition and log WARN messages