[
https://issues.apache.org/jira/browse/AMQ-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821530#comment-13821530
]
Claus Ibsen commented on AMQ-3922:
----------------------------------
Yeah according the hsqldb data type guides we should use BLOB
http://hsqldb.org/doc/guide/sqlgeneral-chapt.html
> HSQLDB support is broken as wrong data type is used in HsqldbJDBCAdapter.java
> -----------------------------------------------------------------------------
>
> Key: AMQ-3922
> URL: https://issues.apache.org/jira/browse/AMQ-3922
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.6.0
> Reporter: Fred Toussi
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 5.10.0
>
>
> The HsqldbJDBCAdaptor defines the SQL type used for storing a lob as "OTHER".
> This is wrong in principle, as this type is intended for storing complex
> serialized objects, not specifically lobs. With this type, the JDBC setObject
> and getObject methods must be used to store and retrieve the object (which is
> not the case with ActiveMQ).
> The problem has been encountered and reported in TOMEE-233 and elsewhere.
> With HSQLDB version 2.x, the type "BLOB" should be used for maximum storage
> capacity and minimum memory use by the database engine. This type is
> supported in all modes of operation, including in-memory and file databases.
> It seems a simple switch from "OBJECT" to "BLOB" in the code should do the
> job, as the JDBC setBytes and getBytes methods used by the superclass are
> compatible with the BLOB type.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
