Result for 5C1F0F8227DF76F067FB42AD883CC4A2E96CF17A

Query result

Key Value
FileName./usr/lib64/swipl-6.2.6/lib/s390x-linux/odbc4pl.so
FileSize67288
MD5193A6A63B8DEE01CA7327BA2E734232E
SHA-15C1F0F8227DF76F067FB42AD883CC4A2E96CF17A
SHA-2565353622FA22298402414744E00BF6FD7B78B737E4B1209571AE1EC74C61B94C0
SSDEEP1536:aXWQFdTUyjVnr/0ZAlQx637uznWB24hgmrveG6u:aXP1VFlQPaBvEG6u
TLSHT18C63F8CAA720C6D6EC713B32D19FA2B243766D347784691DBBACFF0418B2B818D15674
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
MD56E922A639B80CE18FD30391C3C89A25F
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
PackageRelease3.fc19
PackageVersion6.2.6
SHA-17A8CADB8CBB34D657182778910A5C2CEC557D8FA
SHA-256B8FCF3451D83E83D8D52214B474571B382AD1D131A640A9E398B709E2400D21A