1 |
This time with a version constrain that should allow this to expire at |
2 |
some point in the future. |
3 |
|
4 |
Title: GnuCash 2.7+ Breaking Change |
5 |
Author: Aaron W. Swenson <titanofold@g.o> |
6 |
Posted: 2018-01-11 |
7 |
Revision: 1 |
8 |
News-Item-Format: 2.0 |
9 |
Display-If-Installed: <app-office/gnucash-4 |
10 |
|
11 |
Along with changes to use modern libraries, GnuCash 2.7+ has changed the |
12 |
schema [1] it uses for both databases and files. GnuCash will |
13 |
automatically modify the file or database in place upon open. |
14 |
|
15 |
Therefore, it is imperative that you back up any files or databases |
16 |
before using GnuCash 2.7 in case you run into an issue and want or need |
17 |
to revert back to 2.6. |
18 |
|
19 |
Instructions for backing up are as follows: |
20 |
|
21 |
For XML (plain files): |
22 |
$ cp /path/to/file.gnucash /path/to/file.gnucash.bak |
23 |
|
24 |
For MySQL: |
25 |
$ mysqldump gnucash_db | mysql gnucash_db_bak |
26 |
|
27 |
For PostgreSQL: |
28 |
$ createdb -U dbadmin -T gnucash_db -O gnucash_user gnucash_db_bak |
29 |
|
30 |
For SQLite: |
31 |
$ cp /path/to/gnucash/sqlite.file.gnucash /path/to/gnucash/sqlite.file.gnucash.bak |
32 |
|
33 |
[1] https://github.com/Gnucash/gnucash/releases/tag/2.7.0a |