Parents (Total: 10)

The searched file hash is included in 10 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	46282A0688195AC3F9FF0A52D3AC59BB
PackageArch	armv7hl
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	2.fc34
PackageVersion	1.3.0
SHA-1	4ABA74FD294A883C53FB2F66C3090BCB146CB153
SHA-256	C4A65DF5E7024E074D2CB07F62861A79532C030A545D90A999AAFB596782A57D

Key	Value
MD5	FF3BB49BFD099750C927EF3AD40DAE17
PackageArch	armv7hl
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	1.fc33
PackageVersion	1.2.1
SHA-1	46A3AABA8FE33B26370DDF424ACB175B8EC88EE6
SHA-256	CA7EC417D1A37E2ED14F5A160569C053EC832CBFAF4C5CFAC842A5F1EE4D8D68

Key	Value
MD5	257BAE219FEA85607DF596B3C190F0F9
PackageArch	x86_64
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	2.fc34
PackageVersion	1.3.0
SHA-1	2FC4D3AC25443D9E052A6A261A1FEA30708FA8F0
SHA-256	EAD302D19698C063ED28428FACE552589D69A67600A91316C6A7E10BC6AD1C2E

Key	Value
MD5	50595CBCF3858C4DB1EA6B46D1589DC9
PackageArch	noarch
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: – Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. – Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. – Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. – Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/hashicorp/go-memdb
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb-devel
PackageRelease	2.fc34
PackageVersion	1.3.0
SHA-1	316C98B7DF134029F002EFCAF1C96BC7182B6949
SHA-256	5F3FF068C9169CB8F8718730E6D0255E53666000C9699AAB74029092F3ACE342

Key	Value
MD5	72776A2058A508FD4B33F697FB9ECEB3
PackageArch	aarch64
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	2.fc34
PackageVersion	1.3.0
SHA-1	2854D67D345B31FBF6DF423E79F9BD151C9014A0
SHA-256	9B8D482FA30BFB30DCCF23458F4B768BBAAF08F1864BAE77B979793EC289AD7A

Key	Value
MD5	14D972018D4688936655885EF05924CD
PackageArch	noarch
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: – Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. – Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. – Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. – Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/hashicorp/go-memdb
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb-devel
PackageRelease	1.fc33
PackageVersion	1.2.1
SHA-1	A2EED115DEEE4391AA3BF50D873AAAE9946E3FA2
SHA-256	44636C3845600294D6007A078902E687BFAC1C59AA194368E3739D93AD1B654E

Key	Value
FileSize	34608
MD5	826CB13EF94A8F6AF74EC1A592C38AE5
PackageDescription	in-memory database built on immutable radix trees Implementation of a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indicies that exist and allows transactions to be executed.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	golang-github-hashicorp-go-memdb-dev
PackageSection	devel
PackageVersion	1.2.1-1
SHA-1	C4C2487209E14279B9701AC320E2ED237F23AC2E
SHA-256	697CCBA99DDEC7C3638208C52266B6F81F17039968CBA9E15F7BC8D7852783C8

Key	Value
MD5	4B84D75BAAD79BAB75A4CB6679C790B5
PackageArch	x86_64
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	1.fc33
PackageVersion	1.2.1
SHA-1	7DCE6A5C294ABF88F156151C55DF42BBAAA6956C
SHA-256	1764282B9DEA62C8CDBBB1C3096502F0ED821A7B461AA0D5701B9927A701314A

Key	Value
MD5	2A4D11F8381E93A9FB4D03217CAA1398
PackageArch	aarch64
PackageDescription	The Memdb package implements a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indices that exist and allows transactions to be executed. The database provides the following: - Multi-Version Concurrency Control (MVCC) - By leveraging immutable radix trees the database is able to support any number of concurrent readers without locking, and allows a writer to make progress. - Transaction Support - The database allows for rich transactions, in which multiple objects are inserted, updated or deleted. The transactions can span multiple tables, and are applied atomically. The database provides atomicity and isolation in ACID terminology, such that until commit the updates are not visible. - Rich Indexing - Tables can support any number of indexes, which can be simple like a single field index, or more advanced compound field indexes. Certain types like UUID can be efficiently compressed from strings into byte indexes for reduced storage requirements. - Watches - Callers can populate a watch set as part of a query, which can be used to detect when a modification has been made to the database which affects the query results. This lets callers easily watch for changes in the database in a very general way.
PackageMaintainer	Fedora Project
PackageName	golang-github-hashicorp-memdb
PackageRelease	1.fc33
PackageVersion	1.2.1
SHA-1	18560D37D8CFF0898C0D16466F3B3E39A7E9F376
SHA-256	3D80F5FAC98244DECB61E9B7FDC59CBF504674E79BFD7ABE61627361C0D105A3

Key	Value
FileSize	34568
MD5	89C7FA89F97102218CA284B9D84B127D
PackageDescription	in-memory database built on immutable radix trees Implementation of a simple in-memory database built on immutable radix trees. The database provides Atomicity, Consistency and Isolation from ACID. Being that it is in-memory, it does not provide durability. The database is instantiated with a schema that specifies the tables and indicies that exist and allows transactions to be executed.
PackageMaintainer	Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org>
PackageName	golang-github-hashicorp-go-memdb-dev
PackageSection	devel
PackageVersion	1.2.1-1
SHA-1	753CF3F4C0A7B2418C3E5788186BD234D0482D8D
SHA-256	23E1EE910D6EA04AE36BE4699F483C1BD14BD265EBFE10907E87A8F2CBA73FE7