Tree: e29b692b9d

ALLOW_ROOT

master

patch-1

patch-2

0.1

0.10.0

0.10.1

0.10.10

0.10.11

0.10.12

0.10.13

0.10.14

0.10.15

0.10.16

0.10.17

0.10.18

0.10.19

0.10.2

0.10.3

0.10.4

0.10.5

0.10.6

0.10.7

0.10.8

0.10.9

0.11.0

0.11.1

0.11.2

0.11.3

0.11.4

0.2

0.2.1

0.2.2

0.2.3

0.3

0.3.1

0.3.2

0.3.3

0.4

0.4.1

0.4.2

0.4.3

0.5

0.5.1

0.6

0.6.1

0.6.2

0.6.3

0.7

0.7.1

0.7.10

0.7.11

0.7.12

0.7.13

0.7.14

0.7.15

0.7.16

0.7.17

0.7.18

0.7.19

0.7.2

0.7.20

0.7.3

0.7.4

0.7.5

0.7.6

0.7.7

0.7.8

0.7.9

0.8.0

0.8.1

0.8.10

0.8.11

0.8.12

0.8.2

0.8.3

0.8.4

0.8.5

0.8.6

0.8.7

0.8.8

0.8.9

0.9.0

0.9.0a

0.9.1

0.9.10

0.9.11

0.9.12

0.9.13

0.9.14

0.9.15

0.9.16

0.9.17

0.9.18

0.9.19

0.9.2

0.9.20

0.9.21

0.9.22

0.9.23

0.9.3

0.9.4

0.9.5

0.9.6

0.9.7

0.9.8

0.9.9

0.99

0.99.1

0.99.1a

0.99.2

0.99.3

0.99.4

1.0

1.0.1

1.0.10

1.0.11

1.0.12

1.0.13

1.0.14

1.0.15

1.0.16

1.0.17

1.0.2

1.0.3

1.0.4

1.0.5

1.0.6

1.0.7

1.0.8

1.0.8b

1.0.9

1.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'e29b692b9d'

${ noResults }

Commit Graph

3 Commits (e29b692b9dfb51ed03fde3b96abfb99a1faecf0c)

Author	SHA1	Message	Date
Neil Booth	5e1ed3ffa6	Separate history management into its own object - the object also manages unflushed history - the history DB has its own version, starting at 0 This is the first step to making history management into a separate service and to larger block sizes. The next step is an improved history format, which I hope will both save space and be a solution to issue #185. The DB should be able to upgrade in-place without re-syncing the chain.	7 years ago
Neil Booth	74cb4c2f45	Require Python 3.6	8 years ago
Neil Booth	2f26e81629	Implement history compression with tests. Still to do: running compression in background when the flush count reaches a certain level	8 years ago