jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-760) Default blob size for mysql ddl too small
Date Mon, 26 Feb 2007 08:59:05 GMT

     [ https://issues.apache.org/jira/browse/JCR-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-760:
------------------------------

        Fix Version/s:     (was: 1.2.3)
                       1.3
    Affects Version/s:     (was: 1.2.2)

> Default blob size for mysql ddl too small
> -----------------------------------------
>
>                 Key: JCR-760
>                 URL: https://issues.apache.org/jira/browse/JCR-760
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>            Reporter: fabrizio giustina
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: mysql_ddl.diff
>
>
> the default datatype for:
> NODE.NODE_DATA
> PROP.PROP_DATA
> REFS.REFS_DATA 
> in the mysql ddl is "BLOB" which is pretty small to the default size in other dbs.
> When playing with a (not very large) jackrabbit repo using mysql for persistence I easily
got data truncation errors on both NODE.NODE_DATA and PROP.PROP_DATA columns. The same issue
has been reported in the past by other users.
> Although anyone could easily create a custom ddl with larger fields it should be nice
to increase the blob size in the mysql ddl embedded in jackrabbit, in order to avoid this
kind of problems for new users (you usually learn this the hard way, when the number of nodes
in your repository starts to grow and jackrabbit start throwing errors :/).
> Changing BLOB to MEDIUMBLOB will make the default size for mysql more similar to the
one in other dbs, without critically increasing the used space...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message