Bug opened https://bugs.gnucash.org/show_bug.cgi?id=796961
Colin
On Sat, 1 Dec 2018 at 11:51, Geert Janssens wrote:
>
> Op zaterdag 1 december 2018 12:28:54 CET schreef Colin Law:
> > On Sat, 3 Nov 2018 at 20:29, Colin Law wrote:
> > > Should I re-open
On Sat, 1 Dec 2018 at 11:51, Geert Janssens wrote:
>
> Op zaterdag 1 december 2018 12:28:54 CET schreef Colin Law:
> > On Sat, 3 Nov 2018 at 20:29, Colin Law wrote:
> > > Should I re-open https://bugs.gnucash.org/show_bug.cgi?id=796724 and
> > > add the above notes to it?
> >
> > Could I have
Op zaterdag 1 december 2018 12:28:54 CET schreef Colin Law:
> On Sat, 3 Nov 2018 at 20:29, Colin Law wrote:
> > Should I re-open https://bugs.gnucash.org/show_bug.cgi?id=796724 and
> > add the above notes to it?
>
> Could I have some direction on this please? Reopen the above bug or
> open a
On Sat, 3 Nov 2018 at 20:29, Colin Law wrote:
>
> Should I re-open https://bugs.gnucash.org/show_bug.cgi?id=796724 and
> add the above notes to it?
Could I have some direction on this please? Reopen the above bug or
open a new one?
Thanks
Colin
>
> Colin
> On Sat, 13 Oct 2018 at 10:18,
Should I re-open https://bugs.gnucash.org/show_bug.cgi?id=796724 and
add the above notes to it?
Colin
On Sat, 13 Oct 2018 at 10:18, Colin Law wrote:
>
> I have enabled the query log in mysql and when I attempt to save I first see
> 2018-10-13T09:05:13.241000Z5 Connectroot@localhost
I have enabled the query log in mysql and when I attempt to save I first
see
2018-10-13T09:05:13.241000Z5 Connectroot@localhost on gnucash
using Socket
2018-10-13T09:05:13.241249Z5 QuerySET NAMES 'utf8'
2018-10-13T09:05:13.241428Z5 QuerySELECT @@sql_mode
Check your MySQL logs and see if it’s raising error 1007 (database exists)
after the second CREATE DATABASE query. There might be a timing issue where
MySQL is still cleaning up after the DROP DATABASE when the second create query
arrives. If so it might be evident from the MySQL logs.
I am using MySQL. When I attempt to Save As over an existing database
I see the database already exists warning then when I tell it to go
ahead I get the generic server encountered error or bad or corrupt
data message.
In gnucash.trace I see
* 15:40:07 WARN
[GncDbiBackend::session_begin()]
> On Oct 12, 2018, at 6:03 AM, Colin Law wrote:
>
> I believe that on early 3.x versions that it was not possible to Save
> As on top of an existing database of the same name. I thought that
> had been fixed in or before 3.3 but I note that it still fails using
> 3.3 from the Ubuntu 18.10
I believe that on early 3.x versions that it was not possible to Save
As on top of an existing database of the same name. I thought that
had been fixed in or before 3.3 but I note that it still fails using
3.3 from the Ubuntu 18.10 repository. Also I cannot find a bug
referring to the problem.
10 matches
Mail list logo