search

onlinf / google-refine

Automatically exported from code.google.com/p/google-refine
0 stars 0 forks source link

Feature Request: Export SqlDump #205

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Adding an ability to export the project as a SQL dump file[1], possibly in 
MySQL's format, would be beneficial. 

[1] http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html

Original issue reported on code.google.com by mcnamara.tim@gmail.com on 15 Nov 2010 at 1:02

GoogleCodeExporter commented 9 years ago

Original comment by tfmorris on 16 Nov 2010 at 5:47

GoogleCodeExporter commented 9 years ago 
Can this be supported by a template in the templating exporter? I'd imagine 
beside the default json template, we can also generate a wikitext template, and 
perhaps this sql dump file.

Original comment by dfhu...@gmail.com on 16 Nov 2010 at 12:58

GoogleCodeExporter commented 9 years ago 
Should be able to handle with templating exporter.  It will just be a text file 
anyway with a single CREATE statement for the table (per project?).  If folks 
need more than that, then they just use their database's restore options or 
other converter programs on the basic .sql text file generated.

2 options that I could see useful for folks:
1. Supporting COMMENTS statement
2. A checkbox option to include exporting the data & schema or just the schema 
(for testing)

Original comment by thadguidry on 16 Nov 2010 at 3:15

GoogleCodeExporter commented 9 years ago 
If GR can connect and write to a SQL database by using a JDBC bridge, it 
wouldn't be necessary to dump the results as a SQL file. 

Similar to issue: http://code.google.com/p/google-refine/issues/detail?id=12

Original comment by haraldgr...@gmail.com on 22 Dec 2010 at 9:36