New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-1456
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Critical Critical
Assignee: Mike Cannon-Brookes [Atlassian]
Reporter: Joe Walnes
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

EntityEngine cannot create POSITION column on postgres 7.1.3

Created: 16/Mar/03 01:05 PM   Updated: 30/Jul/06 07:34 PM
Component/s: Installation
Affects Version/s: 2.0.2
Fix Version/s: 2.1 Pro

Time Tracking:
Not Specified

Environment: Linux, Resin 2.1.5, Sun JDK 1.4.1, PostgreSQL 7.1.3

Participants: Joe Walnes and Mike Cannon-Brookes [Atlassian]
Since last comment: 5 years, 13 weeks, 6 days ago
Resolution Date: 27/May/03 01:17 AM
Labels:


 Description  « Hide
Upon installation of Jira 2 the following exception occurs on startup:

2003-03-16 18:46:06,543 ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE portletconfiguration (ID NUMERIC(18,0) NOT NULL, PORTALPAGE NUMERIC(18,0), PORTLET_ID VARCHAR(255), COLUMN_NUMBER NUMERIC(9,0), POSITION NUMERIC(9,0), CONSTRAINT PK_portletconfiguration PRIMARY KEY (ID))
Error was: java.sql.SQLException: ERROR: parser: parse error at or near "POSITION"

It seems POSITION is a reserved word in Postgres 7.1.3. I tried this:

> CREATE TABLE TEST (hello VARCHAR(10))
OK

> CREATE TABLE TEST2 (position VARCHAR(10))
ERROR: parser: parse error at or near "position"

I am using field-type-name="postgres" in entityengine.xml (not "postgres72" as this fails with unknown type: TIMESTAMPTZ)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joe Walnes added a comment - 16/Mar/03 02:33 PM
Workaround:
      • WEB-INF/classes/entitydefs/entitymodel.xml Sun Mar 16 18:30:49 2003
      • WEB-INF/classes/entitydefs/entitymodel.xml Sun Mar 16 19:05:46 2003
      • 825,835 ****
        <entity entity-name="PortletConfiguration" table-name="portletconfiguration" package-name="">
        <field name="id" type="numeric" />
        <field name="portalpage" type="numeric" />
        <field name="portletId" type="long-varchar" />
        <field name="columnNumber" type="integer" />
        ! <field name="position" type="integer" />

<prim-key field="id"/>

<relation type="one" title="Parent" rel-entity-name="PortalPage">
<key-map field-name="portalpage" rel-field-name="id"/>
— 825,835 ----
<entity entity-name="PortletConfiguration" table-name="portletconfiguration" package-name="">
<field name="id" type="numeric" />
<field name="portalpage" type="numeric" />
<field name="portletId" type="long-varchar" />
<field name="columnNumber" type="integer" />
! <field name="position" type="integer" col-name="portletPosition" />

<prim-key field="id"/>

<relation type="one" title="Parent" rel-entity-name="PortalPage">
<key-map field-name="portalpage" rel-field-name="id"/>


Mike Cannon-Brookes [Atlassian] added a comment - 27/May/03 01:17 AM
Upgrade to 7.2+ you lazy bastard

This is only a reserved word in 7.1.3 I think, it works fine in 7.1.2 and 7.2.x. If you have to use 7.1.3 - use Joe's workaround.

Cheers,
Mike