Re: [sqlite] Outputting to CSV - row is not quoted when there are no spaces

Thanks Hick, I've actually never hear of Virtual Tables so I'll take a look at play around with this. Thanks, Dan On 2017-06-14 18:44, Hick Gunter wrote: I have found it much simpler and more robust to write a CSV virtual table to handle the formatting. e.g. CREATE VIRTUAL TABLE csv_input

Re: [sqlite] Outputting to CSV - row is not quoted when there are no spaces

Thanks Ketil I'll definitely take a look! FYI my script is available here: https://github.com/64b2b6d12b/spotkey Thanks, Dan On 2017-06-14 18:02, Ketil Froyn wrote: Dan, I'd recommend using a tool that actually understands CSV, and make it parse the input and create new quoted output. I

Re: [sqlite] Expedited vacuum tool?

I've got synchronous = off as the main one. Once in a while I'm tempted for journal_mode = off as well but that's just a little too risky for me, and making a copy to vacuum with it off would be about the same as having it on anyway. Apart from those nothing jumps out as a time saver, either

Re: [sqlite] Expedited vacuum tool?

Regarding: depreciated *temp_store_directory* pragma: It seems that setting your TEMP environment variable to the location of your temporary storage area should let you dispense with the deprecated pragma.

Re: [sqlite] Expedited vacuum tool?

On 15 Jun 2017, at 5:07pm, Keith Medcalf wrote: > > .backup makes a backup of the database file using the backup API call, > effectively copying all the pages (without looking at them to much) from main > to the new file. However, I think this lacks one of the

Re: [sqlite] Expedited vacuum tool?

They both cause a new copy-of-the-source-db file, but... On 2017/06/15 6:07 PM, Keith Medcalf wrote: On Thursday, 15 June, 2017 09:40, David Raymond wrote: In the same train of thought: What's the difference between .backup and .clone in the CLI, and would either

[sqlite] Change 48e086284a76da10a85315bc992e2294bd4711e35ec5a5abaa16e39a6a69d206

For this update is there any particular reason the code was inserted in the middle of the shathree.c code copy in the shell but not added to the shathree.c file itself? --- Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but

Re: [sqlite] Expedited vacuum tool?

On Thursday, 15 June, 2017 09:40, David Raymond wrote: > In the same train of thought: What's the difference between .backup and > .clone in the CLI, and would either of those do the equivalent? > .backup ?DB? FILE Backup DB (default "main") to FILE > .clone NEWDB

[sqlite] Expedited vacuum tool?

After reading the below comment in vacuum.c I'm wondering if anyone has written a simple tool to do the faster vacuum mentioned in the comment? Given of course that no one's going to be accessing the file while it's running. A fair chunk of my stuff tends to be loading a bunch of things into a

Re: [sqlite] imposter tables

Thanks Richard I understand how it works, quite simple really, and knowing they are used by the RBU extension explains why. I am working on a book and I just wanted to understand how/where it could be used where a view, created on the same columns in an index, couldn't be. Paul

Re: [sqlite] imposter tables

On 2017/06/15 10:15 AM, Paul Sanderson wrote: Thanks Richard - the View approach is fine for my needs - just wanted to know what the rationale was for the imposter tables given the ability to simulate the imposter table with a view. I'm thinking the easiest way to describe it is perhaps in