Result for EB1B39E4DB2F8A571467F5A8E50E8DB1E9997616

Query result

Key Value
FileName./usr/lib64/swipl-6.6.6/lib/s390x-linux/odbc4pl.so
FileSize67408
MD5406D05B5E457C0CD32BF1209D4305A7D
SHA-1EB1B39E4DB2F8A571467F5A8E50E8DB1E9997616
SHA-256B4E5898DF18112C7D1DD20436FC0D0B333928435E19D1D0C69AACD5950A1EA44
SSDEEP768:SLvTApaKKZoJuAJclhxZLgQaj3F1UhvqUIdLzwL7gtriczOVjQdUhpDbPQ:s7QaKKZ/p9ax12zIlu2bOKS7D0
TLSHT1EF63E7CBA735D19ACCB07B32C19E52F283763C363684A919AF9CFF1508B76508E26574
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
MD5FF4818D5F59E2062DB02057389AF6290
PackageArchs390x
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
PackageRelease5.fc22
PackageVersion6.6.6
SHA-11F12475A237B26B213A5E06F3A821A9FA391D2FD
SHA-256F9A66F605E48F47E15CD9C731419DE912F1541F7FE2F435BA9AC6B0DEC1832B3