[ http://jira.magnolia.info/browse/MAGNOLIA-1981?page=comments#action_15458 ] David Smith commented on MAGNOLIA-1981: ---------------------------------------
Magnolia only uses Jackrabbit to store data. If there is a bug here, it's with Jackrabbit as Jackrabbit is responsible for all data storage including defining the db schema on first initialization. The advantage of using Jackrabbit is Magnolia doesn't have to know anything about the underlying data store. > Unable to update item due to mysqlDataTruncation exception > ---------------------------------------------------------- > > Key: MAGNOLIA-1981 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1981 > Project: Magnolia > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: Linux Centos 5, tomcat 5.5, jdk1.5.0_09, apache 2, > mod_jk, MySQL 5 > Reporter: Edgar Vonk > Assigned To: Boris Kraft > > If we enter too much (textual) content on a certain page we get the following > exception: > {code} > ERROR info.magnolia.module.admininterface.SaveHandlerImpl 19.12.2007 > 12:30:17 -- /: unable to update item.: failed to write property state: > 55c1ea2e-ed07-4e20-b7f5-b05c720da66b/{}content > javax.jcr.RepositoryException: /: unable to update item.: failed to write > property state: 55c1ea2e-ed07-4e20-b7f5-b05c720da66b/{}content: failed to > write property state: 55c1ea2e-ed07-4e20-b7f5-b05c720da66b/{}content > at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1197) > at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:805) > at > info.magnolia.cms.core.HierarchyManager.save(HierarchyManager.java:525) > at > info.magnolia.module.admininterface.SaveHandlerImpl.save(SaveHandlerImpl.java:212) > at > info.magnolia.module.admininterface.DialogMVCHandler.onSave(DialogMVCHandler.java:284) > at > info.magnolia.module.admininterface.DialogMVCHandler.save(DialogMVCHandler.java:181) > at sun.reflect.GeneratedMethodAccessor156.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > info.magnolia.cms.servlets.MVCServletHandlerImpl.execute(MVCServletHandlerImpl.java:96) > at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > > > CAUSED by: > > mysqlDataTruncation: Data truncation: Data too long for column 'PROP_DATA' at > row 1 > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3374) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3308) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1837) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1961) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2543) > at > com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1737) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2022) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1940) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1925) > {code} > It seems there is a limit in the datamodel for the storage of this content? > Or maybe it is a setting in our MySQL that we need to tweak? Any help is > greatly appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
