| 1 |
2018-01-11 17:27 GMT+01:00 Aaron W. Swenson <titanofold@g.o>: |
| 2 |
|
| 3 |
> This time with a version constrain that should allow this to expire at |
| 4 |
> some point in the future. |
| 5 |
> |
| 6 |
> Title: GnuCash 2.7+ Breaking Change |
| 7 |
> Author: Aaron W. Swenson <titanofold@g.o> |
| 8 |
> Posted: 2018-01-11 |
| 9 |
> Revision: 1 |
| 10 |
> News-Item-Format: 2.0 |
| 11 |
> Display-If-Installed: <app-office/gnucash-4 |
| 12 |
> |
| 13 |
> Along with changes to use modern libraries, GnuCash 2.7+ has changed the |
| 14 |
> schema [1] it uses for both databases and files. GnuCash will |
| 15 |
> automatically modify the file or database in place upon open. |
| 16 |
> |
| 17 |
> Therefore, it is imperative that you back up any files or databases |
| 18 |
> before using GnuCash 2.7 in case you run into an issue and want or need |
| 19 |
> to revert back to 2.6. |
| 20 |
> |
| 21 |
> Instructions for backing up are as follows: |
| 22 |
> |
| 23 |
> For XML (plain files): |
| 24 |
> $ cp /path/to/file.gnucash /path/to/file.gnucash.bak |
| 25 |
> |
| 26 |
> For MySQL: |
| 27 |
> $ mysqldump gnucash_db | mysql gnucash_db_bak |
| 28 |
> |
| 29 |
> For PostgreSQL: |
| 30 |
> $ createdb -U dbadmin -T gnucash_db -O gnucash_user gnucash_db_bak |
| 31 |
> |
| 32 |
> For SQLite: |
| 33 |
> $ cp /path/to/gnucash/sqlite.file.gnucash /path/to/gnucash/sqlite.file. |
| 34 |
> gnucash.bak |
| 35 |
> |
| 36 |
> [1] https://github.com/Gnucash/gnucash/releases/tag/2.7.0a |
| 37 |
> |
| 38 |
|
| 39 |
It could be wise to close GnuCash before backup, also the choice of |
| 40 |
creating a copy of the database is a bit unusual, an offline backup may be |
| 41 |
more appropriated, example for mysql: |
| 42 |
mysqldump gnucash_db | xz > gnucash-2.6.sql.xz |
| 43 |
|
| 44 |
It's ok to leave restore instruction out, since those are usually easy to |
| 45 |
find and spending more time with it does not hurt |
Archives