[
https://issues.apache.org/jira/browse/ROL-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054733#comment-15054733
]
Kohei Nozaki edited comment on ROL-2095 at 12/13/15 12:43 AM:
--------------------------------------------------------------
Nice, I'm glad that {{useFastDateParsing=false}} worked for you :)
I agree with you but I guess it's preferable if 510 -> 520 migration script
takes care of this problem with a way something like that you tried. Because it
might bring some performance degradation as its name states...
Anyway please let me know if any more problem happen in further testing.
FYI: I checked Roller 3.1.0 (Last modified: 2007-04-23, can be obtained from
http://archive.apache.org/dist/roller/roller-3/v3.1.0/bin/ ) that there is no
{{TIMESTAMP}} column in {{mysql/createdb.sql}}.
was (Author: xkylex):
Nice, I'm glad that {{useFastDateParsing=false}} worked for you :)
I agree with you but I guess it's preferable if 510 -> 520 migration script
takes care of this problem with a way something like that you tried. Because it
might bring some performance degradation as its name states...
Anyway it would be appreciated if let me know any more problem happen in
further testing.
FYI: I checked Roller 3.1.0 (Last modified: 2007-04-23, can be obtained from
http://archive.apache.org/dist/roller/roller-3/v3.1.0/bin/ ) that there is no
{{TIMESTAMP}} column in {{mysql/createdb.sql}}.
> 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)
