Repository navigation
Feature Request : Option to not export CREATE TABLE #556
Description
Hi
It would be nice to add an option to only export to SQL the records and not the whole structure of the database ie :
When using menu Export / To SQL add an option like 'Do not export Database/Tables Structure' in order to only have the "INSERT INTO" records in the SQL File.
This can allow exporting full data, make tables structure updates with a blank database, then import new records without having to delete all CREATE TABLE and CREATE INDEX records in the SQL File.
I'm sorry but I don't have sufficient skills to do it myself...
Thanks a lot.
Sorry if I made any mistake, English is not my mother tongue
Activity
export: Allow exporting only the data in an SQL export
MKleusberg commentedon Apr 23, 2016
Hi Laurent
Can you have a look at tomorrow's nightly build (or any later nightly build) and check if the new version is working for you? For downloading a nightly build see the main page of our repository. Please let us know if the new version does the job 😃
elpoolet commentedon Apr 25, 2016
Hi Martin
I just tested the last nightly build.
It works perfectly like I expected!
Thanks a lot ! it'll let me save lot of time !
Just a comment : are the instructions in the out SQL : BEGIN TRANSACTION; and COMMIT; mandatory, since when we import an SQL file created by the Export function it throw an exception : cannot begin a transaction within a transaction ?
Sorry for the OffTopic .... If necessary I'll open a new issue.
Thanks for your reply
justinclift commentedon Apr 25, 2016
Hmmm, it kind of sounds like our code for importing SQL needs to recognise + skip any transaction control statements in the file. Without knowing any better, that doesn't sound too hard. 😉
justinclift commentedon Jul 15, 2016
@elpoolet Is a fix for the exception with "cannot begin a transaction within a transaction" still of interest to you?
A proposed fix for this has been created by @revolter. It would be useful to have some people test it with real data before we add it.
If you're using Windows or OSX, I can build a package with the fix included for people to test.
Interested?
elpoolet commentedon Jul 15, 2016
Hi Justin
Sure I'm always interested.
No problem to test this option with my real data.
Let me know when the build is ready in order I test it.
Thanks a lot.
justinclift commentedon Jul 15, 2016
Sure, are you on Windows or Mac? 😄
justinclift commentedon Jul 15, 2016
@elpoolet If you're on Windows, this should work for you:
http://nightlies.sqlitebrowser.org/win64-onceoffs/DB%20Browser%20for%20SQLite-issue556v1-win64.exe
Please try it out, and let us know if it fixes the exception for you. 😄
justinclift commentedon Jul 19, 2016
@elpoolet ping?
elpoolet commentedon Jul 19, 2016
Sorry,
I had to deal with my car's issues...
Do you have the exe only build..
because I use it as a portable version?
Thanks and please forgive me for the answer dealy..
justinclift commentedon Jul 19, 2016
@elpoolet Sorry, I don't have the capability at the moment to generate the exe-only builds. 😦
It takes a special setup to do it, and we've not needed to get it happening for anything other than the nightly builds. (so far)
elpoolet commentedon Jul 19, 2016
OK.
No problem.
i'll test it on an x64 Windows 7 VM with my real data...
justinclift commentedon Jul 19, 2016
Cool, that would really help. 😄
elpoolet commentedon Jul 22, 2016
Hi,
I just tested functionnality.
Unfortunately, the message is always here.
I used the following sequence :
******Open a freshly xreated database with empty tables
****** Chose the exported SQL file with options : keep column names in
INSERT INTO and Export data only
Then the error is : Error : cannot start a transaction within a transaction
Thanks and sorry for the delay...
justinclift commentedon Jul 22, 2016
Thanks @elpoolet, that makes complete sense. There are two places which can import SQL files and have the bug.
Number 2 might be worth giving a shot.
It probably won't suit large amounts of data though 😦 , because it loads the file into the "Execute SQL" window first.
revolter commentedon Jul 22, 2016
@justinclift, Should we reopen this issue? Or can you solve it based on my partial solution?
justinclift commentedon Jul 22, 2016
@revolter Well, we've kind of already fixed the export part of this issue, but the import part is tracked here for #656. #656 needs to handle File → Import → "Database from SQL File" to be a complete solution. 😄
revolter commentedon Jul 22, 2016
Sorry, pretty tired here, and having two problems on the same issue didn't help me. So, it should be a pretty easy solution if you know where the import is done. But unfortunately I can't do it at all. Do you thing you can manage it? 😄
justinclift commentedon Jul 22, 2016
Yeah, I should be able to cut-n-paste your RegEx into the right spot. Likely tomorrow though... I want to get away from the computer for a bit now.
You're on holiday from tomorrow yeah? If so... have a good one, and hopefully things here haven't exploded in a bad way by the time you're back. 😀
revolter commentedon Jul 22, 2016
Thanks!
Actually, I'm on holiday already, since today was my last work day. And I'm sure nothing will explode 😆
justinclift commentedon Jul 25, 2016
@elpoolet If/when you have a minute to test, the latest nightly build should include the full fix for this.
Any chance you could give it a shot to double check? 😄
elpoolet commentedon Sep 27, 2016
Hi all
I was in vacation till Aug 30th...
After that, had lot of work.
I downloaded stable version 3.9 and all features are in and works like a
charm !!!
Thanks a lot for these improvements... and sorry for my last response
time...
justinclift commentedon Sep 27, 2016
You're welcome @elpoolet. 😄