Where does Gnucash save it backup files when using mysql data source

[L. D. James]

On 07/05/2015 12:56 PM, Colin Law wrote:
> On 5 July 2015 at 17:41, L. D. James <ljames at apollo3.com> wrote:
>> On 07/05/2015 12:23 PM, Colin Law wrote:
>>> Gnucash does create the database for you, so I am not sure what you
>>> are saying.  Creating the database is simple, installing and setting
>>> up the server is not.
>>>>
>>>> Actually Gnucash does not currently create the database.  That feature
>>>> isn't
>>>> implemented yet.  You have to manually create the database and give the
>>>> name
>>>> of the database you created to Gnucash. If you give a name that doesn't
>>>> exist, you'd get an error.
>>> It works ok for me, and has for a long time.  Try it.
>>>
>>> Colin
>> Actually I did.  It gave a generic error message.  I was going to mention
>> that I hope here would be more specific (informative) error messages soon,
>> such as "can't create database", "username or password incorrect", "can't
>> connect to server", etc.
>>
>> Then again, I guess you gave Gnucash root access to your database.
> Certainly not.
>
>> I gave
>> Gnucash access to my username to my database.  I never give any application
>> (even my own userid) root access to mysql.  But that is a matter of
>> preference.  It's something I setup by default.
>>
>> As I think of it, maybe you didn't give root access.  You might have given
>> the id you gave Gnucash the access to create a new database. I'll try that
>> and I'm sure that will work.
> I think so.  You can't expect gnucash to create the database unless
> you give the user you specify that permission.  This just goes to show
> that the complexities of mySQL are not what is required for the simple
> user.
I make more mistakes in using Microsoft word.  I make typos and have 
files lockedup find need to recover them.  I'm glad for the 
availability.  Just because I make a mistake in Microsoft isn't a reason 
to say that simple users shouldn't use it.  I had my nieces and nephews 
doing their homework in Microsoft word when they were younger than 6 
years old.

I'd make many more mistakes trying to handle XML than I ever would using 
Mysql.  I won't tell the gnucash developers to drop XML support just 
because I'm not as fluent with it as I am with Myql.  I hope they will 
implement Mysql, make it easier for them and easier for the user.

>
>> I can do just about anything with a computer, or a database that I can
>> imagine or put into words.  That is why I'm so anxious to see this power
>> implemented into Gnucash.
>>
>> By the way, one of your reasons for having the backup flawed was because by
>> using Mysql, the database might become too big to handle in memory.
> I never said that (or at least never intended it).  I pointed out that
> gnucash is moving away from the 'all in memory' model so it will not
> be so easy for it to do a backup.
I believe implementing some type of backup for an application that has 
important data should be an important component to consider. I'm hoping 
this consideration will catch on.  I'm very much available to help with 
the backup implementation.  It will certainly make giving support for 
Gnucash substantially easier.  I also feel that if it grows, that would 
most likely mean there is more data and a greater lost if the data 
becomes corrupted.  So I would consider that reason to emphasize backups 
even more... not less.

>
>> Personally I would consider, that possibility a concern to move quickly to
>> Mysql.  I wouldn't want to have the accounting system locked down, or
>> limited in size only based on memory.  I would hope that it that potential
>> existed, that someone wanted to handle a large database, they just be able
>> to do it.
>>
>> As far as locked files, I believe the answer would be to backup the data the
>> current user has access to (to the local drive).  If there are locked
>> records, of course he would be limited to only backing up what he already
>> has.  It would, of course (as I imagine) pause on the locked records until
>> they are released and then backup (export) that record.  Eventually all the
>> records would be backedup (exported).
> I am not sure it is that easy to backup a live database which might be
> changing under your feet, and at the same time guarantee that the
> backup represents a consistent snapshot of the data.  But I am not an
> expert in that area.

I have some expertise in that area.  I've been running Online forums and 
giving support for online forums for many years.  I've also spent a lot 
of time recovering corrupted forum data for my clients who have 
problems.  Almost all the forums use mysql as their database resource.  
I'm able to fix and recover the data because of my experience with Mysql 
and working with databases.  I also choose Mysql because of how robust 
it happens to be, and how well supported in the world community it 
happens to be.

I would expect better results recovering data from Mysql resources than 
XML alone.
>
>> Some of the routines as in all developments will have flaws when being
>> developed.  But that's a factor of program development.
>>
>> I hadn't before, but I'll create a new mysql ID for gnucash and give it
>> access to creating databases and let you know how it goes.
>>
>> By the way, I find this ideal in providing access to the office workers.
>> Everyone having access to the database would have their own ID.  If they
>> leave the company we only have to drop that ID. Everyone else can continue
>> using their own access to the accounting system.
>>
>> There are countless pros for using SQL.  It doesn't have to be Mysql, but
>> you can't beat the price and the power.
> Absolutely, for a multi user setup in  an office environment mySQL or
> postgreSQL would be the way to go, but in that case I would expect
> there to be an IT man to sort out any issues.  Most users will not
> need or benefit from that power.
I don't thank a person should have an IT just because they have mysql.  
They would most likely benefit from having an IT because they have 
important documents in Microsoft word.

There are many benefits from having a multiuser environment. Whether 
people have this multiuser environment or not, many people use single 
user environments as if it were multiuser environments and have 
corrupted data and files.  When that happens, they just have to look for 
the latest backup.  If they have an IT department that would make bring 
their data back easier.  It will also help them to have more protection 
from having the problems in the first place.

But again, many places are not going to hire an IT department, perform 
necessary backups, virus protection and other safe guards. The will have 
problems and then go online like here to get support, or call some 
support agency such as mine to help fix their issue.

Not having an IT department should never be a reason not to have a good 
working environment.

I'm describing ways of making Gnucash easy to use for the notice and 
easy to support by the experts.  The features I'm describing will make 
it much easier for me to give support to this group if they experience 
problems.

-- L. James

-- 
L. D. James
ljames at apollo3.com
www.apollo3.com/~ljames