Result for 42B4B7F712A6BC1732DF964B7062F0EAB6804049

Query result

Key Value
FileName./usr/lib/swipl-6.2.6/lib/s390-linux/odbc4pl.so
FileSize57264
MD59E39073ABB355B8A5A3ED7618A41C805
SHA-142B4B7F712A6BC1732DF964B7062F0EAB6804049
SHA-25670D0ADB926F5A4085ACF540D284448ADA59B81B908746869D6AF36D8594BD3E1
SSDEEP768:jihMN3R/CBh4SabNpYEBfOKnhwq/jf0hUyyKW6ixtX:jL3oOvYEOi0hpnW6k
TLSHT1C343188B6231DF7ACDAD537B487F819B1FB158245A1C054F5B4CB26CB8AB7C88843E61
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
MD5302EAD1C27C1F7B4F5AFA2DEA096C6AF
PackageArchs390
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.fc19
PackageVersion6.2.6
SHA-1E08FF1BE38673B9509DE36C9102DA51031610270
SHA-256D57E126C9BEBCB480C6000E53DEFE6450117CE433A012B5A75049008B88E2C40