You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <no...@atlassian.com> on 2007/09/21 14:11:28 UTC

[Roller-JIRA] Resolved: (ROL-1569) Bad characters in PostgreSQL database creation script

     [ http://opensource.atlassian.com/projects/roller/browse/ROL-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Johnson resolved ROL-1569.
--------------------------------

    Resolution: Fixed

Removed bad characters from macros.vm input file:
http://svn.apache.org/viewvc?rev=577981&view=rev

> Bad characters in PostgreSQL database creation script
> -----------------------------------------------------
>
>                 Key: ROL-1569
>                 URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1569
>             Project: Roller
>          Issue Type: Bug
>          Components: Installation
>            Reporter: David Johnson
>            Assignee: David Johnson
>             Fix For: 4.0
>
>
> From Edoardo Panfil:
> "I hope that this can help, I have removed all the caracters that not
> match ( x>=31 && x<=127) || x=='\n')
> 15:    activationcode<WRONG CHAR HERE>varchar(48),
> 80:       action      varchar(16) not null default '<WRONG CHAR HERE>custom'
> 224:    userid<WRONG CHAR HERE><WRONG CHAR HERE>    varchar(48)   not null,
> 226:    time            timestamp with time zone <WRONG CHAR HERE>not null
> 238:    total           integer<WRONG CHAR HERE><WRONG CHAR HERE>  not null,
> 239:    lastused        timestamp with time zone <WRONG CHAR HERE>not null
> 398:    timeleased<WRONG CHAR HERE>    integer,
> 408:    dailyhits<WRONG CHAR HERE>    integer
> Now it workd in with my mac+postgres tomorrow I will do another try with
> linux+postgres
> And from Jonathan Chen:
> I've been trying out Roller 4.0-RC2, and have encountered problems
> with getting a new installation up and running with Postgresql 8. I've
> traced the problem to
> WEB-INF/classes/dbscripts/postgresql/createdb.sql, which has a NUL
> character on line 80, just before the word "custom". Removing the NUL
> allows the d/b creation to suceed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira