Result for 9A539B2CE27C7CBD001F67258D2AE8A5E181187F

Query result

Key Value
FileName./usr/share/gocode/src/github.com/hashicorp/go-memdb/glide.yaml
FileSize151
MD5792344BEBF9969887E73206633310E0A
SHA-19A539B2CE27C7CBD001F67258D2AE8A5E181187F
SHA-2562F51ADE109048884CF98C14702D3D6B7E59524AC22B096C82D202FAAD21F9EC3
SSDEEP3:JSGDFPrQrd9EvKJIMaREpAIb/N59hVTeAMflXAIqeTAA/VWEDFPrQrd9EvKJIIr:xDBr4QvKJIMaEpAm59PepQI9hdDDBr4V
TLSHT1B2C08C82C7A032982F101C06F84C020412264A20B4069AD5B021B26282E04B2021A814
hashlookup:parent-total6
hashlookup:trust80

Network graph view

Parents (Total: 6)

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

Key Value
MD5851E04F7FE3CF03565D572BE518A9E7E
PackageArchnoarch
PackageDescriptionThe 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
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb-devel
PackageRelease4.fc32
PackageVersion1.0.3
SHA-1B27A779A730967C4B8104775E63C756F7E47235E
SHA-256540F1C3153829F72617E0EA073CDA1FCF062E31C32CFF9F95C512914FD6E465D
Key Value
MD5A3822AE2B0835040053B48FAAFD98C42
PackageArcharmv7hl
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.
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb
PackageRelease2.fc34
PackageVersion1.3.0
SHA-1A835F26940543B8B7FB74CE272E60B989D6AB58B
SHA-256C4D7A4D7AFF8383CDCCA6888DCCCD650695D84EF7DE9EB92C2F105B31BCADBE7
Key Value
MD5CB5DF79EA5DB19169B9DA6A4501BB68B
PackageArcharmv7hl
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.
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb
PackageRelease1.fc33
PackageVersion1.2.1
SHA-108FBFBDCD86293CC815D9F65A7F915B02836398A
SHA-256C9625D053CD40B84A8B02E326FFD354B95F38EAD4CED3049031CC2708E8BC625
Key Value
MD514D972018D4688936655885EF05924CD
PackageArchnoarch
PackageDescriptionThe 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
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb-devel
PackageRelease1.fc33
PackageVersion1.2.1
SHA-1A2EED115DEEE4391AA3BF50D873AAAE9946E3FA2
SHA-25644636C3845600294D6007A078902E687BFAC1C59AA194368E3739D93AD1B654E
Key Value
MD550595CBCF3858C4DB1EA6B46D1589DC9
PackageArchnoarch
PackageDescriptionThe 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
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb-devel
PackageRelease2.fc34
PackageVersion1.3.0
SHA-1316C98B7DF134029F002EFCAF1C96BC7182B6949
SHA-2565F3FF068C9169CB8F8718730E6D0255E53666000C9699AAB74029092F3ACE342
Key Value
MD5C57C159CD3C7387258E19A374AC5CAE2
PackageArcharmv7hl
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.
PackageMaintainerFedora Project
PackageNamegolang-github-hashicorp-memdb
PackageRelease4.fc32
PackageVersion1.0.3
SHA-11DDEDE27E9AEF479CB0F3BBFC9202DCA7B82310C
SHA-2569BF1B2D796627C7A6E55190F0242B62643AD3F06F1A6C20EDC9C2B699CB7C552