Fwd: Gnucash file is getting long!

-- Forwarded message -- From: Andrew Shalaurov Date: Tue, Jun 20, 2017 at 12:14 PM Subject: Import Transactions to Gnucash Excised from: Gnucash file is getting long! Can someone explain to me how to import transactions so 2 GL accounts are assigned to each (normal double entry

Re: Import to 2 GL accounts (was: Gnucash file is getting long!)

> On Jun 20, 2017, at 10:14 AM, Andrew Shalaurov wrote: > > Can someone explain to me how to import transactions so 2 GL accounts are > assigned to each (normal double entry accounting) > Ex: cash deposit to a checking account would result in credit principal > (liability), debit cash (from ba

Re: Gnucash file is getting long!

Can someone explain to me how to import transactions so 2 GL accounts are assigned to each (normal double entry accounting) Ex: cash deposit to a checking account would result in credit principal (liability), debit cash (from bank's point of view). I am not clear on the rules assignment... > On

Re: Gnucash file is getting long!

Thanks John, I got it sorted in a more roundabout way, but that was the quick and easy method I was looking for. The file was XML indeed. Regards, Adrien > On Jun 20, 2017, at 11:31 AM, John Ralls wrote: > > > >> On Jun 20, 2017, at 9:06 AM, Adrien Monteleone >> wrote: >> >> I thought I

Re: Gnucash file is getting long!

> On Jun 20, 2017, at 11:26 AM, Geert Janssens > wrote: > > On dinsdag 20 juni 2017 18:06:17 CEST Adrien Monteleone wrote: >> I thought I had set this up with SQLite3, but this does make me question >> that. I tried looking for something that would tell me but I’m not seeing >> it. Certainly, t

Re: Gnucash file is getting long!

> On Jun 20, 2017, at 9:06 AM, Adrien Monteleone > wrote: > > I thought I had set this up with SQLite3, but this does make me question > that. I tried looking for something that would tell me but I’m not seeing it. > Certainly, trying to open the file directly, it is not uncompressed XML. >

Re: Gnucash file is getting long!

On dinsdag 20 juni 2017 18:06:17 CEST Adrien Monteleone wrote: > I thought I had set this up with SQLite3, but this does make me question > that. I tried looking for something that would tell me but I’m not seeing > it. Certainly, trying to open the file directly, it is not uncompressed > XML. You

Re: Gnucash file is getting long!

Note, gnucash.trace contains the following: INFO [gnc_module_init_backend_dbi] Driver: sqlite3 Though I don’t know if this means it is using sqlite3 or just that this driver was found. Regards, Adrien > On Jun 20, 2017, at 11:06 AM, Adrien Monteleone > wrote: > > I thought I had set this

Re: Gnucash file is getting long!

I thought I had set this up with SQLite3, but this does make me question that. I tried looking for something that would tell me but I’m not seeing it. Certainly, trying to open the file directly, it is not uncompressed XML. Is there something in a log file or config file that might indicate whic

Re: Gnucash file is getting long!

On dinsdag 20 juni 2017 17:45:23 CEST Adrien Monteleone wrote: > Geert, > > Is this supposed to be the case for SQLite3 also? Because I’m still seeing > periodic saves based on my preference setting. And I had a crash last week > that resulted in lost changes since the last save. > Yes, As far

Re: Gnucash file is getting long!

Geert, Is this supposed to be the case for SQLite3 also? Because I’m still seeing periodic saves based on my preference setting. And I had a crash last week that resulted in lost changes since the last save. Regards, Adrien > On Jun 20, 2017, at 3:14 AM, Geert Janssens > wrote: > > There a

Re: Gnucash file is getting long!

There are no automatic saves in the sql backend any more. Or rather every change you make is saved automatically and immediately. So the autosave delaus you experience on the xml backend don't happen when using sql. The initial loadtime on the other hand turns out to be slower. This should impro

Re: Gnucash file is getting long!

On 2017-06-16, Derek Atkins wrote: > Adam Funk writes: > >>> Not necessarily. The "default" backend would be SQLite, which is a DB >>> that stores into a single file. So it will act like the current XML >>> backend in terms of storage, but not necessarily the same with backup >>> files. Howeve

Re: Gnucash file is getting long!

For interactive use disk I/O is fast compared to the time waiting for keystrokes. Only for importing and possibly report generation would disk I/O be a bottleneck. Currently the file size slows down startup because the entire file is read and interpreted into memory. If the file were simply a

Re: Gnucash file is getting long!

If the MySql format data file is not on the main hard drive but a) on a USB 2.0 or 3.0 key, b) on another computer accessed by Wi-Fi or Ethernet, c) on a cloud server. Would the MySql database format be faster than the compressed XML in any of the above scenarios, particularly when periodic automa

Re: Gnucash file is getting long!

On 2017-06-17 12:04, John Ralls wrote: > >> On Jun 17, 2017, at 10:22 AM, AC > > wrote: >> >> On 2017-06-17 00:07, Colin Law wrote: >>> On 17 June 2017 at 02:31, AC >> > wrote: On 2017-06-16 09:35, Derek Atkins wrote: > Adam Funk mai

Re: Gnucash file is getting long!

> On Jun 17, 2017, at 10:22 AM, AC wrote: > > On 2017-06-17 00:07, Colin Law wrote: >> On 17 June 2017 at 02:31, AC wrote: >>> On 2017-06-16 09:35, Derek Atkins wrote: Adam Funk writes: >> Not necessarily. The "default" backend would be SQLite, which is a DB >> that stores

Re: Gnucash file is getting long!

On 2017-06-17 00:07, Colin Law wrote: > On 17 June 2017 at 02:31, AC wrote: >> On 2017-06-16 09:35, Derek Atkins wrote: >>> Adam Funk writes: >>> > Not necessarily. The "default" backend would be SQLite, which is a DB > that stores into a single file. So it will act like the current XML

Re: Gnucash file is getting long!

> On Jun 17, 2017, at 12:07 AM, Colin Law wrote: > > On 17 June 2017 at 02:31, AC > wrote: >> On 2017-06-16 09:35, Derek Atkins wrote: >>> Adam Funk writes: >>> > Not necessarily. The "default" backend would be SQLite, which is a DB > that stores into a si

Re: Gnucash file is getting long!

On 17 June 2017 at 02:31, AC wrote: > On 2017-06-16 09:35, Derek Atkins wrote: >> Adam Funk writes: >> Not necessarily. The "default" backend would be SQLite, which is a DB that stores into a single file. So it will act like the current XML backend in terms of storage, but not ne

Re: Gnucash file is getting long!

On 2017-06-16 09:35, Derek Atkins wrote: > Adam Funk writes: > >>> Not necessarily. The "default" backend would be SQLite, which is a DB >>> that stores into a single file. So it will act like the current XML >>> backend in terms of storage, but not necessarily the same with backup >>> files.

Re: Gnucash file is getting long!

Adam Funk writes: >> Not necessarily. The "default" backend would be SQLite, which is a DB >> that stores into a single file. So it will act like the current XML >> backend in terms of storage, but not necessarily the same with backup >> files. However no server is required. > > Great! Thanks

Re: Gnucash file is getting long!

On 2017-06-15, Derek Atkins wrote: > Adam, > > On Thu, June 15, 2017 8:29 am, Adam Funk wrote: >> On 2017-06-14, Colin Law wrote: >> >>> Hopefully, thanks to the hard work of the developers, within just a >>> few years the full database functionality will be implemented and >>> load/save should be

Re: Gnucash file is getting long!

Adam, On Thu, June 15, 2017 8:29 am, Adam Funk wrote: > On 2017-06-14, Colin Law wrote: > >> Hopefully, thanks to the hard work of the developers, within just a >> few years the full database functionality will be implemented and >> load/save should be very much improved. > > Is this going to invo

Re: Gnucash file is getting long!

On 15 June 2017 at 13:29, Adam Funk wrote: > On 2017-06-14, Colin Law wrote: > ... >> Hopefully, thanks to the hard work of the developers, within just a >> few years the full database functionality will be implemented and >> load/save should be very much improved. > > Is this going to involve a d

Re: Gnucash file is getting long!

On 2017-06-14, Colin Law wrote: > On 14 June 2017 at 12:33, David Carlson wrote: >> ... >> My solution so far has been to buy a more powerful computer and use Ethernet >> instead of WiFi to attach to the data file. Yes, a file save through WiFi >> takes well over a minute for my data file which

Re: Gnucash file is getting long!

in the archive about closing the books and using or not using a new file as it comes up each year. David Cousens -- View this message in context: http://gnucash.1415818.n4.nabble.com/Gnucash-file-is-getting-long-tp4692169p4692181.html Sent from the GnuCash - User mailing list archive at

Re: Gnucash file is getting long!

Please use Reply All (or similar) when replying to this list, otherwise your reply just goes to the previous poster. I am copying it to the list here. See also comments below. On 14 June 2017 at 17:00, George Riner wrote: > Just for comparison... > > My gnucash file is 4.7 Mb (compressed XML) on

Re: Gnucash file is getting long!

On 14 June 2017 at 12:33, David Carlson wrote: > ... > My solution so far has been to buy a more powerful computer and use Ethernet > instead of WiFi to attach to the data file. Yes, a file save through WiFi > takes well over a minute for my data file which is now over 6MB compressed. Hopefully,

Re: Gnucash file is getting long!

I think that John Ogden has a valid question which should be covered better somewhere in the manual. The short answer, unfortunately, is that there is no way to split out old data to shrink the data file. Also, it is a fact that eventually your file may grow to the point where it taxes your compu

Re: Gnucash file is getting long!

What do you mean by 'quite large'? I have 15 years of (personal) data in mine and would not split it unless force to. It is great to be able to so easily look back to see when and where I bought the dishwasher (or whatever) and how much it cost. Mine is1.9 MBytes (compressed xml). Colin On 14 Jun

Gnucash file is getting long!

I have been using GnuCash for over four years, and the file is becoming quite large.I have searched the documentation but have failed to find any instructions for separating the GnuCash accounts file (for all accounts) so that I end up with two files, one for 'old' transactions and one for 'new'