diff --git a/src/1.1.0/operations/specs.md b/src/1.1.0/operations/specs.md index f4fd0bb6e4..8604aeeccd 100644 --- a/src/1.1.0/operations/specs.md +++ b/src/1.1.0/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.2.1/operations/specs.md b/src/1.2.1/operations/specs.md index f4fd0bb6e4..8604aeeccd 100644 --- a/src/1.2.1/operations/specs.md +++ b/src/1.2.1/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.2.2/operations/specs.md b/src/1.2.2/operations/specs.md index f92967f922..0e27d7e7de 100644 --- a/src/1.2.2/operations/specs.md +++ b/src/1.2.2/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.2.3/operations/specs.md b/src/1.2.3/operations/specs.md index f92967f922..0e27d7e7de 100644 --- a/src/1.2.3/operations/specs.md +++ b/src/1.2.3/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.2.4/operations/specs.md b/src/1.2.4/operations/specs.md index f92967f922..0e27d7e7de 100644 --- a/src/1.2.4/operations/specs.md +++ b/src/1.2.4/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.3.0/operations/specs.md b/src/1.3.0/operations/specs.md index 277cd197ef..6668a8909a 100644 --- a/src/1.3.0/operations/specs.md +++ b/src/1.3.0/operations/specs.md @@ -4,9 +4,9 @@ immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.3.1/immudb.md b/src/1.3.1/immudb.md index 3e006f00d5..062d137a73 100644 --- a/src/1.3.1/immudb.md +++ b/src/1.3.1/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.3.2/immudb.md b/src/1.3.2/immudb.md index 3e006f00d5..062d137a73 100644 --- a/src/1.3.2/immudb.md +++ b/src/1.3.2/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.4.0/immudb.md b/src/1.4.0/immudb.md index 3e006f00d5..062d137a73 100644 --- a/src/1.4.0/immudb.md +++ b/src/1.4.0/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.4.1/immudb.md b/src/1.4.1/immudb.md index 3e006f00d5..062d137a73 100644 --- a/src/1.4.1/immudb.md +++ b/src/1.4.1/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.5.0/immudb.md b/src/1.5.0/immudb.md index 3e006f00d5..062d137a73 100644 --- a/src/1.5.0/immudb.md +++ b/src/1.5.0/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.9DOM.0/immudb.md b/src/1.9DOM.0/immudb.md index a0de5b4d5a..abeb5c6efd 100644 --- a/src/1.9DOM.0/immudb.md +++ b/src/1.9DOM.0/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/1.9DOM.1/immudb.md b/src/1.9DOM.1/immudb.md index a0de5b4d5a..abeb5c6efd 100644 --- a/src/1.9DOM.1/immudb.md +++ b/src/1.9DOM.1/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements. diff --git a/src/master/immudb.md b/src/master/immudb.md index a0de5b4d5a..abeb5c6efd 100644 --- a/src/master/immudb.md +++ b/src/master/immudb.md @@ -97,9 +97,9 @@ Check [auditor](production/auditor.md) section for additional details. immudb is an append-only, tamperproof database with key/value and SQL (Structured Query Language) application programming interfaces. -The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (1^64 - 1). +The immudb core persistence layer consists of a cryptographically-immutable log. Transactions are sequentially stored and uniquely identified by unsigned 64-bit integer values, thus setting a theoretical limit of 18446744073709551615 transactions (2^64 - 1). -In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (1^64 - 1). +In order to provide manageable limits, immudb is designed to set an upper bound to the number of key-value pairs included in a single transaction. The default value being 1024, so using default settings, the theoretical number of key-value pairs that can be stored in immudb is: 1024 * (2^64 - 1). We designed immudb to require stable resources but not imposing strong limitations as most of the settings can be adjusted based on the use-case requirements.