| Key | Value |
|---|---|
| FileName | ./usr/lib/.build-id/2e/00dd4c801bcb783aba5dfdec675af0073482ad |
| FileSize | 29 |
| MD5 | 77DB8916122E1CE430A63928B6B7A67D |
| SHA-1 | E8E6409A8CE9F10151FD1250AE27B9A10A4604B1 |
| SHA-256 | 6FBE74331FD8C1AF189FC37F4E9067E94DA633B052CE19758C87636DDA4F23BD |
| SSDEEP | 3:gCDN2RGOL:XEj |
| TLSH | |
| hashlookup:parent-total | 9 |
| hashlookup:trust | 95 |
The searched file hash is included in 9 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 | 7F7B018D1E7E94FC85B2057EEA15D9B1 |
| 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 | 4.fc32 |
| PackageVersion | 1.0.3 |
| SHA-1 | DC47B00609B48E6215C16D321A674EB88EFE9BFD |
| SHA-256 | C70DD1381C0CA015B82BCE3ADA1319EBBE25AED8968B2C55A8C57693A6A97A86 |
| 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 | 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 | 1AB05CD5D69D9D3667A48AB23DACB244 |
| 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 | 4.fc32 |
| PackageVersion | 1.0.3 |
| SHA-1 | E996D66551EF9FE6EB62B83ADD8CBB03BB43E3AC |
| SHA-256 | 84A1DAEA401AA29D7EDA3486429A851DDCD37D241B754A086F48343A57527C26 |
| 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 |
|---|---|
| MD5 | C7E032E414D1832285AC4C6BFAD09C8A |
| 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 | 4.fc32 |
| PackageVersion | 1.0.3 |
| SHA-1 | 5E93F80F5345D0B50D7D21F73C2ED0E30C7E1128 |
| SHA-256 | E584E114153C9DCC0562862BC2AFE63AFD585A2BCC95E8AF64934D413943FA5A |