Result for A6E2FE319C1AE22C208A19ECC07D21FBE2BE3CF1

Query result

Key Value
FileName./usr/lib/.build-id/7f/75664045e37acebc77ccc8c99373dbc51ab8c9
FileSize59
MD5917E9DADA00592956B82A49031B79DA6
SHA-1A6E2FE319C1AE22C208A19ECC07D21FBE2BE3CF1
SHA-2563D04B22429D8DD040C1352C6B6244D33E8E238F3AD9F2A8B21A2D9E1E4FD24BD
SSDEEP3:gCD/WQEK+IT6mwRjiKn:X/WQj+IWm4p
TLSHT1A1A00260957C3657BD253D612D240C1CF3568D40B379DF40C4AC41FB82550445241C59
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD55EFE6C6875552196550BE563C1D3F502
PackageArcharmv7hl
PackageDescriptionThe value of RDMS for Prolog is often over-estimated, as Prolog itself can manage substantial amounts of data. Nevertheless a Prolog/RDMS interface provides advantages if data is already provided in an RDMS, data must be shared with other applications, there are strong persistency requirements or there is too much data to fit in memory. The popularity of ODBC makes it possible to design a single foreign-language module that provides RDMS access for a wide variety of databases on a wide variety of platforms. The SWI-Prolog RDMS interface is closely modeled after the ODBC API. This API is rather low-level, but defaults and dynamic typing provided by Prolog give the user quite simple access to RDMS, while the interface provides the best possible performance given the RDMS independency constraint.
PackageMaintainerFedora Project
PackageNamepl-odbc
PackageRelease1.fc34
PackageVersion8.2.4
SHA-17FBECE6C7C063860269E5D14EEB8610540B1E949
SHA-256FFA9542FCF31F26ECEC62AAF84BB1D926010DF83AF35FC15B0A80A671E702A20