Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export using SQL insert #36

Open
xarg opened this issue Jul 24, 2015 · 55 comments
Open

Export using SQL insert #36

xarg opened this issue Jul 24, 2015 · 55 comments

Comments

@xarg
Copy link

xarg commented Jul 24, 2015

Would be great to be able to export a table using SQL inserts. Right now only CSV seems to be available. Copy Special is great, but works only for the selected rows, not for whole tables.

Or if SQL inserts are hard to implement, perhaps just importing CSV would be nice.
How I do it now: COPY table FROM 'xxxx.csv' DELIMITER ',' CSV;

@eightyfive
Copy link

+1 preventing me from buying the full version

@adi-
Copy link

adi- commented Sep 2, 2015

+1

1 similar comment
@trapias
Copy link

trapias commented Sep 22, 2015

+1

@eightyfive
Copy link

pg_dump -U username -d databasename > outputfile.sql

@astewart-twist
Copy link

+1 @jakob you should consider using https://www.bountysource.com/ for crowd funding feature requests like these.

@xarg
Copy link
Author

xarg commented Dec 3, 2015

@astewart-twist: This is not an OS project so I don't think @jakob can use bountysource (maybe other similar platforms exist?) (https://github.com/bountysource/core/wiki/Frequently-Asked-Questions).

I hope I'm not going too off-topic but, I would say the best way to support the development is to buy the app or recommending it. Since I bought the app already I'm just gonna recommend it: https://twitter.com/humanfromearth/status/672559977446416385

I encourage you to do the same!

@ncolyer
Copy link

ncolyer commented Dec 4, 2015

I also purchased the product and wanted to add that I also would like to see an SQL export feature. There are certain instances where I do not have access to pgdump and therefore the ability to do some from Postico would be great. I would pay extra to have had this feature had I known it was not native in the app. Love the product, just wish it was more complete.

@jakob
Copy link
Owner

jakob commented Dec 4, 2015

I have a short question for everyone: would it be useful if I implemented a feature to just export the data as INSERT statements (like the copy special command), rather than creating a full SQL dump like pg_dump does? Exporting just the data would be much easier to implement than creating a full SQL dump.

@xarg
Copy link
Author

xarg commented Dec 4, 2015

For me INSERT statements are more than enough.

@ncolyer
Copy link

ncolyer commented Dec 4, 2015

I concur.

Nicholas Colyer

On Dec 4, 2015, at 2:12 PM, Alex Plugaru notifications@github.com wrote:

For me INSERT statements are more than enough.


Reply to this email directly or view it on GitHub.

@eightyfive
Copy link

I also agree INSERTs are enough. I mean definitely much better than nothing!

On Sat, Dec 5, 2015 at 2:16 AM, Nicholas Colyer notifications@github.com
wrote:

I concur.
Nicholas Colyer

On Dec 4, 2015, at 2:12 PM, Alex Plugaru notifications@github.com wrote:

For me INSERT statements are more than enough.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub:
#36 (comment)

@g3d
Copy link

g3d commented Jan 16, 2016

+1 for this feature.
I also purchased the product and wanted to add SQL export feature into it.

@jacobbullock
Copy link

+1 for import / export of sql.

@punkratz312
Copy link

+1

@cupnoodle
Copy link

+1, really hope this feature can be implemented.

@rexzhang
Copy link

+1 for import / export of sql.

@jbreuer95
Copy link

+1

1 similar comment
@francoisbruneau
Copy link

+1

@xarg
Copy link
Author

xarg commented Jan 20, 2017

While having MacBook Pro Touchbar support #311 is cool, I'm really disappointed seeing it done while an issue like the current one or more importantly #82 have almost 2 years since are reported and nothing was done about it so far. @jakob can you give us an update on this? What's happening?

@jakob
Copy link
Owner

jakob commented Jan 21, 2017

@xarg I'm sorry to hear you're not happy with the pace of development.

I try to prioritise features according to the impact they have versus the amount of effort required. Touch Bar is high impact & low effort, so it was a great first task for Chris, who is just getting started with Postico development.

Adding SQL export is a bit more effort, even though most of the parts are already there. Considering how many people support this issue, it was probably a mistake to delay this so long, and I should have started sooner. I'll see what I can do.

Currently I'm finalising the graphical index editor (#19) and trying to get the 1.1 update with lots of bug fixes out the door, but that release is blocked by an issue with Core Graphics on macOS 10.10 that I still need to work around. Meanwhile, Chris has started to work on CSV import (#68).

@xarg
Copy link
Author

xarg commented Jan 23, 2017

Thanks for your detailed reply @jakob. I appreciate it.

@atMari
Copy link

atMari commented Feb 3, 2017

+1

@jakob jakob modified the milestone: v1.2 Mar 23, 2017
@rensverschuren
Copy link

rensverschuren commented Apr 11, 2017

+ 1

@billyshena
Copy link

billyshena commented May 23, 2017

+1

2 similar comments
@schuon
Copy link

schuon commented Jul 14, 2017

+1

@lloydh
Copy link

lloydh commented Aug 18, 2017

+1

@tobyhinloopen
Copy link

+1

@cokron
Copy link

cokron commented Nov 2, 2017

+1 - very disappointed that this feature is not available. I bought Postico, thinking about using an alternative package. Other than that, great tool!

@terehov
Copy link

terehov commented Jan 3, 2018

+1

3 similar comments
@ctoLarsson
Copy link

+1

@bingimar
Copy link

bingimar commented Feb 5, 2018

+1

@jidesakin
Copy link

+1

@ghost
Copy link

ghost commented Mar 6, 2018

+1 It is more than 2 years already.

@thorntonjohn
Copy link

+1 just want sql inserts, nothing fancy.

@kidbrax
Copy link

kidbrax commented May 3, 2018

+1

3 similar comments
@rouralberto
Copy link

+1

@pyrat
Copy link

pyrat commented Aug 8, 2018

+1

@jjhesk
Copy link

jjhesk commented Aug 17, 2018

+1

@bed42
Copy link

bed42 commented Nov 2, 2018

+1 :)

@Jaspur
Copy link

Jaspur commented Mar 15, 2019

👍

4 similar comments
@FedeGens
Copy link

+1

@pwm
Copy link

pwm commented May 31, 2019

+1

@aazcast
Copy link

aazcast commented Aug 2, 2019

+1

@stevenleeg
Copy link

+1

@striveforbest
Copy link

Oh how nice would it be to be able to dump the entire database into a file!

@karam-nus
Copy link

karam-nus commented Oct 15, 2019

+1 for sql inserts

@andresilvagomez
Copy link

  • 1

@leobenkel
Copy link

+1

2 similar comments
@devglrd
Copy link

devglrd commented Aug 16, 2020

+1

@juliofalbo
Copy link

+1

@barttenbrinke
Copy link

+1 :) That is the last thing preventing me from buying it :)

@isavita
Copy link

isavita commented Apr 9, 2021

+1

@jakob
Copy link
Owner

jakob commented Apr 9, 2021

Since we keep getting requests for this feature, I would like to ask for some feedback.

  1. Do you really want to just export INSERT statements to a file, or do you want full dumps (including CREATE TABLE statements etc)
  2. Can you explain how you would use this feature in a few sentences?
  3. Is using CSV Export / Import a possible alternative?

Background:
Most people who contact us via email with similar feature requests want a way to create full dumps (like pg_dump creates). These full dumps would contain both CREATE TABLE statements and INSERT statements. Implementing this feature would be a major undertaking and something that we just do not have the capacity for. Also, there's already pg_dump which does exactly what people want, so I don't see a strong argument for adding this feature to Postico. It would be convenient to have it built in, but it wouldn't really allow new workflows that currently aren't possible.

For us this feature currently doesn't have a high priority, but maybe we are missing some important scenarios how this feature would be useful, so please let us know how you would use this feature!

@Jaspur
Copy link

Jaspur commented Apr 9, 2021 via email

@tobyhinloopen
Copy link

tobyhinloopen commented Apr 9, 2021

  1. Do you really want to just export INSERT statements to a file, or do you want full dumps (including CREATE TABLE statements etc)

Basically I'd want both:

  • CREATE TABLE + INSERTS (full copy)
  • only INSERTs (data dump) (--data-only)
  • only CREATE TABLEs (structure dump) (--schema-only)
  1. Can you explain how you would use this feature in a few sentences?

I would use it to:

  • copy and sync database schemas and data between databases
  • import SQL dumps i've received elsewhere
  • share SQL dumps with other people
  1. Is using CSV Export / Import a possible alternative?

Also a nice feature, but for me it wouldn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests