You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-dev@incubator.apache.org by "Shanti Subramanyam (JIRA)" <ji...@apache.org> on 2009/09/14 20:26:57 UTC
[jira] Updated: (OLIO-109) timezone fields in schema are
inconsistent
[ https://issues.apache.org/jira/browse/OLIO-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shanti Subramanyam updated OLIO-109:
------------------------------------
Fix Version/s: (was: 0.2)
0.3
There are many more schema inconsistencies between the versions, so postponing this to 0.3 or beyond.
> 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.