Result for 49D661E577CE1AB4EE1D4BD417484411576CE07A

Query result

Key Value
FileName./usr/lib/.build-id/17/47d4ff0943e654ff1496dfd51b576507096b93
FileSize59
MD502AF6D31C09BE2AC264B1FBC968C7478
SHA-149D661E577CE1AB4EE1D4BD417484411576CE07A
SHA-256E2A522C72009CCEAF413B5C62AA5B936B04C494AFE5D826228E6A45CD270EA15
SSDEEP3:gCD/WyIT6mwRjiKn:X/WyIWm4p
TLSHT14FA00260917C3656BD257D611D240C1CF3568D40F33EDF40C4AC41FB82550549242C59
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
MD58E6FBCBD060D7D69DD7AB8E1734B6954
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
PackageRelease4.fc33
PackageVersion8.2.1
SHA-1E0C56BA9028D7D3BB213D1CF5838BEDFC5E05906
SHA-2565F132850F0AAF4350B1A0F71E5D93C4C4F40C106D1D31C0BCFD67904F88B4128