Re: PG Migration Wizard

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Mark Levene" <Mark(at)UnderGlass(dot)co(dot)nz>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: PG Migration Wizard
Date: 2003-03-31 19:03:17
Message-ID: 03AF4E498C591348A42FC93DEA9661B8259EA9@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi Mark,

Currently this functionality has not been implemented as it proved
during testing to cause more problems than it was work (expressions are
not always compatible).

I might revisit it sometime, but it's fairly low on my list I'm afraid.
In the meantime, you can edit the column defaults manually - a pain, but
hopefully you need only do it once.

Regards, Dave.

-----Original Message-----
From: Mark Levene [mailto:Mark(at)UnderGlass(dot)co(dot)nz]
Sent: 31 March 2003 05:13
To: pgadmin-support(at)postgresql(dot)org
Subject: [pgadmin-support] PG Migration Wizard


Hi

The "Default" values don't seem to come across from an Access
database using the PG Migration Wizard, (except for the "autonumber
fields").

For example, using the Migration Wizard to bring the tables
across, I get

---snip---
"StartRange" integer,
"EndRange" integer,
"StartDate" date,
"EndDate" date,
---snip---

whereas, I wanted

---snip---
"StartRange" integer DEFAULT 0,
"EndRange" integer DEFAULT 0,
"StartDate" date DEFAULT now(),
"EndDate" date DEFAULT '2299-12-31'::date,
---snip---

Now, I could go and check each table, however it would be great
if they came across.

Thanks for a wonderful product (which I will continue to say
until hell freezes over!)


Thanks,
Mark ...

Browse pgadmin-support by date

  From Date Subject
Next Message Stéphane Coville 2003-04-01 14:48:02
Previous Message Mark Levene 2003-03-31 04:12:40 PG Migration Wizard