| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |
| Date: | 2004-08-13 06:52:05 |
| Message-ID: | 411C6515.6070105@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>>Being able to export to other dbs will get us _more_ users, not less.
>
> Without some type of corresponding import utility that seems logically false.
Nope. Consider it like this. How many companies are going to move to
PostgreSQL from Oracle if they cannot dump their data back to Oracle as
a failsafe? Very few. How many people will use PostgreSQL if they know
they cannot dump it over to MySQL or anything easily if they want to.
Trying to "tie in" users is pre-opensource / big commercial company
thinking.
What if they have a mixed environment, and they want to be able to give
data and dumps from postgres to their MySQL people?
Consider that no companies switched to MS Excel when it was first
invented UNTIL it could export BACK to Lotus. Otherwise, how could they
give their Excel files to other users in the office who hadn't upgraded yet?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | strk | 2004-08-13 10:09:30 | Dump Version |
| Previous Message | Robert Treat | 2004-08-13 06:15:05 | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2004-08-13 07:47:36 | ALTER INDEX |
| Previous Message | Robert Treat | 2004-08-13 06:15:05 | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |