https://bugs.gnucash.org/show_bug.cgi?id=798992 Reports that after upgrading to
MariaDB 11 on their servers, two Windows users are unable to work with their
GnuCash databases. GnuCash appears to connect but DBI thinks that numeric
variables are strings and, since it's expecting numbers,
Having problems
Server setup in AWS
When 'save as' the Local host Version into the AWS endpoint Msgbox becomes
non responsive and eventually crashes GnuCash
The tables in cloud db are setup but I can excess any data.
And I can open the cloud db in the Gnucash UI but no accounts (as expected)
That may work fine for a single instance of gnucash. However, it this is 2
instances of gnucash on 2 separate computers, does libdbi provide any
notification mechanism to notify gnucash on computer #2 that computer #1
has written to the db?
On Mon, Nov 5, 2018 at 2:39 AM craigarno wrote:
>
Geert Janssens-4 wrote
> Op zondag 4 november 2018 14:49:22 CET schreef craigarno:
>> Geert Janssens-4 wrote
>>
> Whether it can work depends on
> whether the db layer we rely on has a notification mechanism for db
> changes we
> can hook into. The current db layer is provided by libdbi, which
Geert Janssens-4 wrote
> Op zondag 4 november 2018 04:36:30 CET schreef craigarno:
> The only part I have no idea about at this stage is how to tell all views
> to refresh when one user makes a change.
If you are headed toward C++, the "Observer" Design Pattern may be able to
get the "refresh
Op zondag 4 november 2018 04:36:30 CET schreef craigarno:
> My application is similar, except two of my users will be outside of my
> local network, working from the Internet. I'm a tiny one man SOHO
> operation who is off-site a lot of the time and may also be accessing my
> GnuCash database
My application is similar, except two of my users will be outside of my local
network, working from the Internet. I'm a tiny one man SOHO operation who
is off-site a lot of the time and may also be accessing my GnuCash database
remotely and concurrently from a job site providing client
Gnucash will put a lock on the database as long as it's in use by one user. If
a second user tries to open it that user will be presented with a warning tje
db is still in use by ssomeone else. So you can't accidentally be working on an
open db with two users at once. If you ignore the warning
I'd like to understand if gnucash + mysql supports avoiding simultaneous
editors (e.g., via locks).
In more detail:
I want to keep accounts for a small organisation in which we've decided
several people should have access to the books for transparency and
distribution of work. One possibility
