[
https://issues.apache.org/jira/browse/ROL-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046874#comment-15046874
]
Kohei Nozaki commented on ROL-2095:
-----------------------------------
This might help: adding {{useFastDateParsing=false}} to JDBC url.
References:
http://stackoverflow.com/questions/10273870/cannot-convert-value-2012-04-05-102000-from-column-xx-to-timestamp
http://www.liferay.com/web/guest/community/forums/-/message_boards/message/361354
> Roller 510 -> 520 migration is incomplete for TIMESTAMPS
> --------------------------------------------------------
>
> Key: ROL-2095
> URL: https://issues.apache.org/jira/browse/ROL-2095
> Project: Apache Roller
> Issue Type: Bug
> Reporter: David Johnson
> Assignee: Roller Unassigned
>
> In SVN commit 1680531 we added to mysql.properties these two lines:
> TIMESTAMP_SQL_TYPE_NULL=datetime(3) NULL
> TIMESTAMP_SQL_TYPE=datetime(3)
> Those lines effectively changed the type of all timestamp columns in Roller
> from timestamp to datetime(3), but we offer no migration to convert timestamp
> data to datatime(3) format.
> This will cause Roller to fail to work with errors like this:
> [EL Warning]: 2015-12-06 16:09:42.61--UnitOfWork(659709738)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLException: Cannot convert value '2014-11-27
> 10:25:01.000' from column 8 to TIMESTAMP.
> Error Code: 0
> Call: SELECT id, about, isactive, allowcomments, analyticscode, blacklist,
> creator, datecreated, defaultallowcomments, defaultcommentdays,
> defaultplugins, editorpage, editortheme, emailaddress, emailcomments,
> enablebloggerapi, enablemultilang, displaycnt, handle, icon, lastmodified,
> locale, commentmod, name, showalllangs, tagline, timeZone, visible,
> bloggercatid FROM weblog WHERE (handle = ?)
> bind => [1 parameter bound]
> Query: ReadAllQuery(name="Weblog.getByHandle" referenceClass=Weblog
> sql="SELECT id, about, isactive, allowcomments, analyticscode, blacklist,
> creator, datecreated, defaultallowcomments, defaultcommentdays,
> defaultplugins, editorpage, editortheme, emailaddress, emailcomments,
> enablebloggerapi, enablemultilang, displaycnt, handle, icon, lastmodified,
> locale, commentmod, name, showalllangs, tagline, timeZone, visible,
> bloggercatid FROM weblog WHERE (handle = ?)")
> We should either revert the datetime(3) change or add a migration for all
> fields effected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
