[
https://issues.apache.org/jira/browse/OLIO-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759305#action_12759305
]
Kim LiChong commented on OLIO-109:
----------------------------------
Current bug fix causes SQL DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException:
Unknown column 'TIMEZONE' in 'field list'
Error Code: 1054
Need to remove timezone field in SocialEvent as JPA looks for this field in
database. The timezone adjustment is made in EventRestAction.java
See Related bug Olio-Issue 118
Committed revision 818648.
> timezone fields in schema are inconsistent
> ------------------------------------------
>
> Key: OLIO-109
> URL: https://issues.apache.org/jira/browse/OLIO-109
> Project: Olio
> Issue Type: Bug
> Components: generic
> Affects Versions: 0.1
> Reporter: Shanti Subramanyam
> Assignee: Shanti Subramanyam
> Priority: Minor
> Fix For: 0.3
>
>
> Jim Larus reports:
> In the schema for the DB, the timezone in the PERSON class is a 25-char
> string, while the timezone field in SOCIALEVENT is 100-char string. Some of
> the timezones in includes/timezones.html are longer than 25 char, so I
> suspect the latter is correct.
> Both the php and rails schema use a 25-char string in PERSON, where as the
> Java app uses 255 (which is probably an overkill). Only the PHP app has
> timezone in the SOCIALEVENT table - the other two apps don't.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
