Save As MySQL is crashing gnucash

[Ian X Waddington]

HI, whilst this is a fascinating discussion and I am sure useful for future
development could I ask we get back on topic and help me find out why my
installation of GnuCash simply crashes out when trying to save-as MySQL.

Either no one has 2.3.17 working with MySQL 5.1.53 on a Windows 7  32bit
machine because there is a bug, or there is something wrong with my install
or how I am going about it.

Either way it shouldn't crash so I will report it as a bug.

Any pointers appreciated, just a small clue would help :-)

Regards

-----Original Message-----
From: gnucash-user-bounces at gnucash.org
[mailto:gnucash-user-bounces at gnucash.org] On Behalf Of Geert Janssens
Sent: 27 November 2010 09:18
To: gnucash-user at gnucash.org
Cc: Gnucash Devel
Subject: Re: Save As MySQL is crashing gnucash

On Friday 26 November 2010, Robert Heller wrote:
> At Fri, 26 Nov 2010 11:51:18 -0800 (PST) Phil Longstaff
<plongstaff at rogers.com> wrote:
> > That's not quite OK.  If a new version of gnucash is released which 
> > requires a changed db schema, gnucash will try to automatically add 
> > new columns and constraints.  This might mean we will need to 
> > package schema upgrades as a separate utility to be run by the dba.
> 
> There is no reason to disallow a *user* from adding/dropping tables or 
> altering tables (adding/removing columns, etc.).  Allowing mere 
> *users* the privs to add/drop *databases* is the security issue.  The 
> gnucash application should not be creating the database itself, only
tables, etc.
> 
As said before, this all depends on the context.

I have only two things to add regarding creation and dropping rights:

1. MySql's privilege system is very fine grained. It can be configured
perfectly fine to have a certain user only master a limited set of databases
- including creation and deletion of those databases - while the same user
doesn't have any privileges on other databases. That leaves a nice
middleground for some use cases.

2. Environments with strict security policies still need an administrator
account for their database server, only known to a limited set of
administrators. I think that in such environments, it will indeed be an
administrator that initially sets up the database and other users access it
via less privileged accounts. As John already suggested, in such
environments an administrator should run GnuCash and open the db once after
each gnucash update. I believe it would be sufficient to document this
clearly.


Geert
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.