[
https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676633#comment-16676633
]
Rob Godfrey commented on QPID-8257:
-----------------------------------
[~alex.rufous] but that is a choice at a higher level of the code... we never
pass null into AbstractJDBCMessageStore::addContent (because that would NPE :-)
).
I think the safest thing is to confine the change to the Sybase JDBC
implementation. Separately we could make the decision about whether to simply
omit a content record when there is no content, though that may have other
implications.
> Sybase message store not supporting empty messages
> --------------------------------------------------
>
> Key: QPID-8257
> URL: https://issues.apache.org/jira/browse/QPID-8257
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.3
> Reporter: Olivier VERMEULEN
> Priority: Major
>
> Unlike other databases Sybase default nullability for a column is "NOT NULL".
> And since we don't specify anything when creating the QPID_MESSAGE_CONTENT
> table, the "content" column defaults to "NOT NULL".
> So when we send an empty message, this constraint is broken and we receive a
> SybSQLException...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
