You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/04/03 11:13:41 UTC

[jira] [Commented] (ARTEMIS-1084) Oracle12C has table name size limit of 30 chars. When using paging and a table name of >10 chars. Artemis will work fine, until it's Page UUID size goes above 20 chars. Then start failing to page.

    [ https://issues.apache.org/jira/browse/ARTEMIS-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953292#comment-15953292 ] 

ASF subversion and git services commented on ARTEMIS-1084:
----------------------------------------------------------

Commit 7e4cb4d1813b6f4f5bc5ae28bc7cd194dad5d14a in activemq-artemis's branch refs/heads/1.x from [~martyntaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=7e4cb4d ]

ARTEMIS-1084 Throw RunTime on bad Oracle table size

(cherry picked from commit 42bf845)


> Oracle12C has table name size limit of 30 chars.  When using paging and a table name of >10 chars.  Artemis will work fine, until it's Page UUID size goes above 20 chars.  Then start failing to page.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1084
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1084
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Martyn Taylor
>
> We need to ensure that table size is appropriate for Oracle12C when paging.  10chars max



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)