Another issue with that migrate script is, contrary to the comment here:
-- alter the pbsp (pop-before-smtp) table
CREATE SEQUENCE dbmail_pbsp_idnr_seq;
CREATE TABLE dbmail_pbsp (
idnr INT8 NOT NULL DEFAULT NEXTVAL('dbmail_pbsp_idnr_seq'),
since TIMESTAMP NOT NULL DEFAULT '1970-01-01 00:00:00',
ipnumber INET NOT NULL DEFAULT '0.0.0.0',
PRIMARY KEY (idnr)
);
CREATE UNIQUE INDEX dbmail_idx_ipnumber ON dbmail_pbsp(ipnumber);
CREATE INDEX dbmail_idx_since ON dbmail_pbsp(since);
the pbsp table is actually not altered at all, but a new dbmail_pbsp
table is created (leaving pbsp in existance, and thereafter unused).
As it's transient data anyways, maybe just "drop table pbsp;" and don't
worry about a correct alter?
Jesse
On Thu, 2006-07-20 at 16:36 -0600, Jesse Norell wrote:
> Hello,
>
> We're finally starting to migrate from 1.2 and I ran across a problem
> in the migration script (both 2.0 and 2.1) if you don't already have the
> auto_notifications or auto_replies tables.
>
>
> --- migrate_from_1.x_to_2.0.pgsql Thu Jul 20 15:11:55 2006
> +++ migrate_from_1.x_to_2.0.pgsql.fix Thu Jul 20 16:33:12 2006
> @@ -28,6 +28,7 @@
> CREATE SEQUENCE auto_notification_seq;
> CREATE TABLE auto_notifications (
> auto_notify_idnr INT8 DEFAULT nextval('auto_notification_seq'),
> + user_idnr INT8 DEFAULT '0' NOT NULL,
> notify_address VARCHAR(100),
> PRIMARY KEY (auto_notify_idnr)
> );
> @@ -35,6 +36,7 @@
> CREATE SEQUENCE auto_reply_seq;
> CREATE TABLE auto_replies (
> auto_reply_idnr INT8 DEFAULT nextval('auto_reply_seq'),
> + user_idnr INT8 DEFAULT '0' NOT NULL,
> reply_body TEXT,
> PRIMARY KEY(auto_reply_idnr)
> );
>
>
>
--
Jesse Norell - [EMAIL PROTECTED]
Kentec Communications, Inc.
