Ticket #85 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

2 minor problems with Postgres v1.3.0->1.4.0 DB schema update

Reported by: stavros Assigned to: areski
Priority: blocker Milestone: milestone Version 1.4
Component: Database Version: Trunk 1.4
Keywords: Postgres SQL schema update Cc: stavros@phreaker.net

Description

Trying a fresh install of v1.4.0 for testing I found a couple of little problems in the Postgres update script:

psql:UPDATE-a2billing-v1.3.0-to-v1.4.0-pgsql.sql:17: NOTICE:  CREATE
 TABLE / PRIMARY KEY will create implicit index
 "cc_card_subscription_pkey" for table "cc_card_subscription"

CREATE TABLE
psql:UPDATE-a2billing-v1.3.0-to-v1.4.0-pgsql.sql:19: ERROR:  multiple
 primary keys for table "cc_card_subscription" are not allowed

ALTER TABLE
psql:UPDATE-a2billing-v1.3.0-to-v1.4.0-pgsql.sql:22: ERROR:  syntax error
 at or near "INTEGER" at character 46

The attached .diff fixes both these problems, and applies cleanly against the recent changeset 132 too.

Attachments

v1.4.0.Postgres.schema.diff (1.0 kB) - added by stavros on 08/06/07 07:00:47.

Change History

08/06/07 07:00:47 changed by stavros

  • attachment v1.4.0.Postgres.schema.diff added.

08/06/07 10:11:08 changed by stavros

  • status changed from new to closed.
  • resolution set to fixed.

08/17/07 08:05:23 changed by ewrtwet

  • summary changed from 2 minor problems with Postgres v1.3.0->1.4.0 DB schema update to 2 minor problems with Postgres v1.3.0->1.4.0 DB schema update.


Google