Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-12-01 Thread Colin Law 
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  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?
> >
>
> As we haven't determined if it's really the same bug I propose to create a new
> one and reference the closed one.
>
> Regards,
>
> Geert
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-12-01 Thread Colin Law 
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 some direction on this please?  Reopen the above bug or
> > open a new one?
> >
>
> As we haven't determined if it's really the same bug I propose to create a new
> one and reference the closed one.

OK, will do, I don't think it is the same cause, just the same
symptom.  It is often not obvious whether a bug report should relate
to the symptom or the cause.

Thanks

Colin
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-12-01 Thread Geert Janssens 
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 new one?
> 

As we haven't determined if it's really the same bug I propose to create a new 
one and reference the closed one.

Regards,

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-12-01 Thread 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 new one?

Thanks

Colin

>
> 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 on gnucash 
> > using Socket
> > 2018-10-13T09:05:13.241249Z5 QuerySET NAMES 'utf8'
> > 2018-10-13T09:05:13.241428Z5 QuerySELECT @@sql_mode
> > 2018-10-13T09:05:13.241746Z5 QuerySET 
> > sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> > 2018-10-13T09:05:13.241903Z5 QueryCREATE TEMPORARY TABLE 
> > numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
> > 2018-10-13T09:05:13.242534Z5 QueryINSERT INTO numtest VALUES 
> > (-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
> > 2018-10-13T09:05:13.242779Z5 QuerySELECT * FROM numtest
> > 2018-10-13T09:05:13.243032Z5 QueryDROP TABLE numtest
> > 2018-10-13T09:05:13.243496Z5 QuerySHOW TABLES FROM `gnucash`
> > 2018-10-13T09:05:13.243955Z5 Quit
> >
> > Then it shows the db already exists warning.  When I tell it to go ahead I 
> > see
> > 2018-10-13T09:05:29.411367Z6 Connectroot@localhost on gnucash 
> > using Socket
> > 2018-10-13T09:05:29.411622Z6 QuerySET NAMES 'utf8'
> > 2018-10-13T09:05:29.411817Z6 QuerySELECT @@sql_mode
> > 2018-10-13T09:05:29.412095Z6 QuerySET 
> > sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> > 2018-10-13T09:05:29.412250Z6 QueryCREATE TEMPORARY TABLE 
> > numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
> > 2018-10-13T09:05:29.413159Z6 QueryINSERT INTO numtest VALUES 
> > (-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
> > 2018-10-13T09:05:29.413459Z6 QuerySELECT * FROM numtest
> > 2018-10-13T09:05:29.413756Z6 QueryDROP TABLE numtest
> > 2018-10-13T09:05:29.414040Z6 QuerySHOW TABLES FROM `gnucash`
> > 2018-10-13T09:05:29.414333Z6 Init DBmysql
> > 2018-10-13T09:05:29.414405Z6 QueryDROP DATABASE `gnucash`
> > 2018-10-13T09:05:33.727523Z7 Connectroot@localhost on gnucash 
> > using Socket
> >
> > and nothing else.  There is a few seconds gap after the drop database 
> > before the Connect line and the error message on screen.
> >
> > Colin
> >
> >
> >
> > On Fri, 12 Oct 2018 at 17:12, John Ralls  wrote:
> >>
> >> 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.
> >>
> >> Regards,
> >> John Ralls
> >>
> >>
> >> > On Oct 12, 2018, at 7:45 AM, Colin Law  wrote:
> >> >
> >> > 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()] Databse already exists, Might
> >> > clobber it.
> >> > * 15:41:37  CRIT 
> >> > [GncDbiBackend::session_begin()] Unable to create database
> >> > 'gnucash'
> >> >
> >> > If I then look in mysql I see that the database has been dropped, and
> >> > if I try to Save As again it creates the database correctly.  So it
> >> > appears the drop database is working but then it is unable to create
> >> > the new one for some reason after dropping, but is able to create it
> >> > if it does not need to drop it.
> >> > On Fri, 12 Oct 2018 at 15:29, John Ralls  wrote:
> >> >>
> >> >>
> >> >>
> >> >> 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 repository.  Also I cannot find a bug
> >> >> referring to the problem.
> >> >>
> >> >> Can someone elucidate?
> >> >>
> >> >>
> >> >> Colin,
> >> >>
> >> >> The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 for 
> >> >> MySQL/MariaDB and https://bugs.gnucash.org/show_bug.cgi?id=789594 for 
> >> >> SQLite3.
> >> >>
> >> >> What DB Engine are you using and do you get an error or is it just 
> >> >> refusing to drop the existing DB?
>

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-11-03 Thread Colin Law 
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 on gnucash 
> using Socket
> 2018-10-13T09:05:13.241249Z5 QuerySET NAMES 'utf8'
> 2018-10-13T09:05:13.241428Z5 QuerySELECT @@sql_mode
> 2018-10-13T09:05:13.241746Z5 QuerySET 
> sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> 2018-10-13T09:05:13.241903Z5 QueryCREATE TEMPORARY TABLE numtest 
> ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
> 2018-10-13T09:05:13.242534Z5 QueryINSERT INTO numtest VALUES 
> (-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
> 2018-10-13T09:05:13.242779Z5 QuerySELECT * FROM numtest
> 2018-10-13T09:05:13.243032Z5 QueryDROP TABLE numtest
> 2018-10-13T09:05:13.243496Z5 QuerySHOW TABLES FROM `gnucash`
> 2018-10-13T09:05:13.243955Z5 Quit
>
> Then it shows the db already exists warning.  When I tell it to go ahead I see
> 2018-10-13T09:05:29.411367Z6 Connectroot@localhost on gnucash 
> using Socket
> 2018-10-13T09:05:29.411622Z6 QuerySET NAMES 'utf8'
> 2018-10-13T09:05:29.411817Z6 QuerySELECT @@sql_mode
> 2018-10-13T09:05:29.412095Z6 QuerySET 
> sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
> 2018-10-13T09:05:29.412250Z6 QueryCREATE TEMPORARY TABLE numtest 
> ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
> 2018-10-13T09:05:29.413159Z6 QueryINSERT INTO numtest VALUES 
> (-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
> 2018-10-13T09:05:29.413459Z6 QuerySELECT * FROM numtest
> 2018-10-13T09:05:29.413756Z6 QueryDROP TABLE numtest
> 2018-10-13T09:05:29.414040Z6 QuerySHOW TABLES FROM `gnucash`
> 2018-10-13T09:05:29.414333Z6 Init DBmysql
> 2018-10-13T09:05:29.414405Z6 QueryDROP DATABASE `gnucash`
> 2018-10-13T09:05:33.727523Z7 Connectroot@localhost on gnucash 
> using Socket
>
> and nothing else.  There is a few seconds gap after the drop database before 
> the Connect line and the error message on screen.
>
> Colin
>
>
>
> On Fri, 12 Oct 2018 at 17:12, John Ralls  wrote:
>>
>> 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.
>>
>> Regards,
>> John Ralls
>>
>>
>> > On Oct 12, 2018, at 7:45 AM, Colin Law  wrote:
>> >
>> > 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()] Databse already exists, Might
>> > clobber it.
>> > * 15:41:37  CRIT 
>> > [GncDbiBackend::session_begin()] Unable to create database
>> > 'gnucash'
>> >
>> > If I then look in mysql I see that the database has been dropped, and
>> > if I try to Save As again it creates the database correctly.  So it
>> > appears the drop database is working but then it is unable to create
>> > the new one for some reason after dropping, but is able to create it
>> > if it does not need to drop it.
>> > On Fri, 12 Oct 2018 at 15:29, John Ralls  wrote:
>> >>
>> >>
>> >>
>> >> 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 repository.  Also I cannot find a bug
>> >> referring to the problem.
>> >>
>> >> Can someone elucidate?
>> >>
>> >>
>> >> Colin,
>> >>
>> >> The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 for 
>> >> MySQL/MariaDB and https://bugs.gnucash.org/show_bug.cgi?id=789594 for 
>> >> SQLite3.
>> >>
>> >> What DB Engine are you using and do you get an error or is it just 
>> >> refusing to drop the existing DB?
>> >>
>> >> Regards,
>> >> John Ralls
>> >>
>>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more inform

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-10-13 Thread Colin Law 
 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
2018-10-13T09:05:13.241746Z5 QuerySET
sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
2018-10-13T09:05:13.241903Z5 QueryCREATE TEMPORARY TABLE
numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
2018-10-13T09:05:13.242534Z5 QueryINSERT INTO numtest VALUES
(-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
2018-10-13T09:05:13.242779Z5 QuerySELECT * FROM numtest
2018-10-13T09:05:13.243032Z5 QueryDROP TABLE numtest
2018-10-13T09:05:13.243496Z5 QuerySHOW TABLES FROM `gnucash`
2018-10-13T09:05:13.243955Z5 Quit

Then it shows the db already exists warning.  When I tell it to go ahead I
see
2018-10-13T09:05:29.411367Z6 Connectroot@localhost on gnucash
using Socket
2018-10-13T09:05:29.411622Z6 QuerySET NAMES 'utf8'
2018-10-13T09:05:29.411817Z6 QuerySELECT @@sql_mode
2018-10-13T09:05:29.412095Z6 QuerySET
sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
2018-10-13T09:05:29.412250Z6 QueryCREATE TEMPORARY TABLE
numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )
2018-10-13T09:05:29.413159Z6 QueryINSERT INTO numtest VALUES
(-9223372036854775807, 9223372036854775807, 1.79769213486e+307)
2018-10-13T09:05:29.413459Z6 QuerySELECT * FROM numtest
2018-10-13T09:05:29.413756Z6 QueryDROP TABLE numtest
2018-10-13T09:05:29.414040Z6 QuerySHOW TABLES FROM `gnucash`
2018-10-13T09:05:29.414333Z6 Init DBmysql
2018-10-13T09:05:29.414405Z6 QueryDROP DATABASE `gnucash`
2018-10-13T09:05:33.727523Z7 Connectroot@localhost on gnucash
using Socket

and nothing else.  There is a few seconds gap after the drop database
before the Connect line and the error message on screen.

Colin



On Fri, 12 Oct 2018 at 17:12, John Ralls  wrote:

> 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.
>
> Regards,
> John Ralls
>
>
> > On Oct 12, 2018, at 7:45 AM, Colin Law  wrote:
> >
> > 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()] Databse already exists, Might
> > clobber it.
> > * 15:41:37  CRIT 
> > [GncDbiBackend::session_begin()] Unable to create database
> > 'gnucash'
> >
> > If I then look in mysql I see that the database has been dropped, and
> > if I try to Save As again it creates the database correctly.  So it
> > appears the drop database is working but then it is unable to create
> > the new one for some reason after dropping, but is able to create it
> > if it does not need to drop it.
> > On Fri, 12 Oct 2018 at 15:29, John Ralls  wrote:
> >>
> >>
> >>
> >> 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 repository.  Also I cannot find a bug
> >> referring to the problem.
> >>
> >> Can someone elucidate?
> >>
> >>
> >> Colin,
> >>
> >> The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 for
> MySQL/MariaDB and https://bugs.gnucash.org/show_bug.cgi?id=789594 for
> SQLite3.
> >>
> >> What DB Engine are you using and do you get an error or is it just
> refusing to drop the existing DB?
> >>
> >> Regards,
> >> John Ralls
> >>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-10-12 Thread John Ralls 
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.

Regards,
John Ralls


> On Oct 12, 2018, at 7:45 AM, Colin Law  wrote:
> 
> 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()] Databse already exists, Might
> clobber it.
> * 15:41:37  CRIT 
> [GncDbiBackend::session_begin()] Unable to create database
> 'gnucash'
> 
> If I then look in mysql I see that the database has been dropped, and
> if I try to Save As again it creates the database correctly.  So it
> appears the drop database is working but then it is unable to create
> the new one for some reason after dropping, but is able to create it
> if it does not need to drop it.
> On Fri, 12 Oct 2018 at 15:29, John Ralls  wrote:
>> 
>> 
>> 
>> 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 repository.  Also I cannot find a bug
>> referring to the problem.
>> 
>> Can someone elucidate?
>> 
>> 
>> Colin,
>> 
>> The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 for 
>> MySQL/MariaDB and https://bugs.gnucash.org/show_bug.cgi?id=789594 for 
>> SQLite3.
>> 
>> What DB Engine are you using and do you get an error or is it just refusing 
>> to drop the existing DB?
>> 
>> Regards,
>> John Ralls
>> 

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-10-12 Thread Colin Law 
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()] Databse already exists, Might
clobber it.
* 15:41:37  CRIT 
[GncDbiBackend::session_begin()] Unable to create database
'gnucash'

If I then look in mysql I see that the database has been dropped, and
if I try to Save As again it creates the database correctly.  So it
appears the drop database is working but then it is unable to create
the new one for some reason after dropping, but is able to create it
if it does not need to drop it.
On Fri, 12 Oct 2018 at 15:29, John Ralls  wrote:
>
>
>
> 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 repository.  Also I cannot find a bug
> referring to the problem.
>
> Can someone elucidate?
>
>
> Colin,
>
> The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 for 
> MySQL/MariaDB and https://bugs.gnucash.org/show_bug.cgi?id=789594 for SQLite3.
>
> What DB Engine are you using and do you get an error or is it just refusing 
> to drop the existing DB?
>
> Regards,
> John Ralls
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-10-12 Thread John Ralls 



> 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 repository.  Also I cannot find a bug
> referring to the problem.
> 
> Can someone elucidate?

Colin,

The bugs were https://bugs.gnucash.org/show_bug.cgi?id=796724 
 for MySQL/MariaDB and 
https://bugs.gnucash.org/show_bug.cgi?id=789594 
 for SQLite3.

What DB Engine are you using and do you get an error or is it just refusing to 
drop the existing DB?

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

[GNC] V3.3 on Ubuntu 18.10 can't Save As over existing mysql database

2018-10-12 Thread Colin Law 
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.

Can someone elucidate?

Colin
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.