Result for DDE4993F0C666B8802C2E02A4F6111EE69C9CB28

Query result

Key Value
FileName./usr/lib/.build-id/75/7a26c441fcfef294201a0e86dc5990b378cace
FileSize61
MD5797599EA68B817E6B6D787CA8C855D40
SHA-1DDE4993F0C666B8802C2E02A4F6111EE69C9CB28
SHA-256F88DD63120C62D00824E1E8CD7D475EEE132E89EA78F3EB8356A53537F5D9659
SSDEEP3:gCD/bj6pJd76XRjiKn:X/bWnGp
TLSHT159A0027546B8B214B5713DE12E181C4837716D50B374DF61C09E417A81551594241C74
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
MD55FD209C42F75804652CB3734678AEFBF
PackageArchx86_64
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
PackageRelease3.fc32
PackageVersion8.0.3
SHA-168F208FF2F07584C7AEF7AFF3F216BEFF772B506
SHA-256300EA754C19CD6568E5AD804A036BD686EE52F0B15152E312F233AB4AA9769FE