From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Exporting sql scripts in pgAdmin |
Date: | 2013-02-24 09:53:02 |
Message-ID: | 1361699582.2245.13.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, 2013-01-24 at 11:45 +0100, Lukasz Brodziak wrote:
> Hi,
>
> Following Dave Page's advice I'd like raise an idea for a feature that
> would allow users to export table rows as INSERT statements. The idea
> behind this feature is that we are not always able to use COPY TO/COPY FROM
> to move data between databases and generating and insert statement based on
> SELECT result is the answer. It could be an option in 'Execute to file'
> menu option something like "Export as INSERT script" that after checking
> would add INSERT INTO <table from select> (columns which we already export)
> VALUES(values we already export). As a future feature thare can be an
> option added to input the specific table name if the destination db has the
> same table defined under different name.
> The feature is implemented in EMS SQL Manager for PostgreSQL but buying it
> just for this option is madness. Besides it's better to put new features
> into our favourite program than to support the competition :)
>
OK. I'm not sure you mean you want to work on this, or that you want us
to put this in our TODO list?
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2013-02-25 10:20:30 | pgAdmin III commit: Fix the display of extension owner names. |
Previous Message | Guillaume Lelarge | 2013-02-23 18:24:53 | pgAdmin III commit: Add a title to the backup and restore windows |