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

[Colin Law]

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 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.

>
> 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.

>
> 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.

Colin