Result for 8C12585D75CF439B4EC57CAA78F6D78127E568C9

Query result

Key Value
FileName./usr/lib/.build-id/7e/21a9085a96b25beba7f17b05440bd44b750776
FileSize59
MD541337C3F2C2A0CCBBA836C8CA91C333E
SHA-18C12585D75CF439B4EC57CAA78F6D78127E568C9
SHA-256A35C32C46E97F89AC3854A6093248B063FB740F252F25A36BD9AF13046CD51DB
SSDEEP3:gCD/UpJd+IT6mwRjiKn:X/UnAIWm4p
TLSHT15EA00270957C3656F9213D611D240C1CF366AD40B379DF50C4EC42BB81550445241C54
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
MD5F28CFAC499AA75E79086C78CA83B2E6E
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
PackageRelease3.fc32
PackageVersion8.0.3
SHA-1E412AD40F10FB02C35325C082603BA28CD6A7907
SHA-25671D2E07BB91FE0EC4B3AE6F583FD40A6726DC2666198A32C22044AC31E0A01C3