| From: | "Juliet May" <jmay(at)speark(dot)com> |
|---|---|
| To: | "Cheryl Thompson" <cthompso(at)ci(dot)irving(dot)tx(dot)us>, <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Had to drop some table columns, managed to annoy MS |
| Date: | 2003-01-13 23:12:40 |
| Message-ID: | 014d01c2bb59$45011ee0$a1d2a8c0@impsu.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
I use pgadmin II to access postgresql and they have a sweet little plugin
called the Database Migration Wizard which lets you export access tables as
well as a variety of others. It uses the odbc driver so I don't know if it
will work around your problem but it might be a try. Either way, I find
pgAdmin II makes my life a lot simpler when it comes to working with
postgresql.
Julie
----- Original Message -----
From: "Cheryl Thompson" <cthompso(at)ci(dot)irving(dot)tx(dot)us>
> Is there a way to copy/export the DB (or it's tables) to another DB and
dump
> all this stuff that's causing the problems? In particular, in the past I
> have exported the entirety of a database into a flat file and imported it
> into a "clean" version.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-01-13 23:18:09 | Re: Had to drop some table columns, managed to annoy MS |
| Previous Message | Lex Berezhny | 2003-01-13 23:12:31 | Re: Had to drop some table columns, managed to annoy MS |