sqlitebrowser-recipe

sqlitebrowser-recipe:v3.11.x

  1. Git
  2. lp:sqlitebrowser-recipe
  3. v3.11.x
Last commit made on 2019-04-03
Get this branch:
git clone -b v3.11.x https://git.launchpad.net/sqlitebrowser-recipe

Branch merges

Branch information

Name:
v3.11.x
Repository:
lp:sqlitebrowser-recipe

Recent commits

f07dafd... by Justin Clift

Update version number to 3.11.2

5ff520c... by Justin Clift

Added Korean translation updates from PR #1600

d389a62... by Giuseppe Zizza <email address hidden>

Italian translation for v3.11.x

cc9bd1b... by Justin Clift

Regenerate translation files for the v3.11.x branch

e2ad545... by FriedrichFroebel <email address hidden>

Updated German translation for 3.11.x

8f9d2bd... by Justin Clift

Merge pull request #1830 from bernardosulzbach/pt-br-update

Updated Brazilian Portuguese translation

5095dee... by Bernardo Sulzbach <email address hidden>

Updated Brazilian Portuguese translation

4fd8d86... by Martin Kleusberg <email address hidden>

Fix editing encryption when using SQLCipher 4

It seems like we need to explicitly detach the newly encrypted database
when changing the encryption settings and using SQLCipher 4.

See issue #1829.

aed9809... by Martin Kleusberg <email address hidden>

Fix multiple problems in 0f6946c19dacb4900336bc3d043f70a3608501f7

Fix multiple problems which were introduced in commit
0f6946c19dacb4900336bc3d043f70a3608501f7. They all are about detection
of transaction statements. First it turned out that the commit slightly
changed the behaviour of the dirty parameter which, although there did
not seem to be any consequences of this, was turned back into the old
behaviour. Then the detection of transaction statements depended on the
structure updated flag which is totally wrong and needed to be fixed.
Next, it turned out that SQLite executed ";COMMIT;" as one statement
instead of two. This means we need to skip until after the first
semicolon and not until before it. And finally, after skipping until
after the semicolon we should perform the check for transaction
statements again before blindly giving the next statement to SQLite.

See issue #1777.

66c8c59... by Martin Kleusberg <email address hidden>

Fix bug in 0f6946c19dacb4900336bc3d043f70a3608501f7

Fix a stupid mistake in commit 0f6946c19dacb4900336bc3d043f70a3608501f7.
Apparently I wasn't able to count to 6.