Result for F67E8B1EFA585BAC03EB5B3A4857710BDC86E4CC

Query result

Key Value
FileName./usr/lib/swipl-6.0.2/lib/powerpc-linux/odbc4pl.so
FileSize70784
MD58DCD64B99A9CFB76F411A137446B15A1
SHA-1F67E8B1EFA585BAC03EB5B3A4857710BDC86E4CC
SHA-25697237E3CFFF3572BAC57993FED8493C4767DC66AADE9E721C8B07EFAEB902317
SSDEEP1536:H5CLY/xpneiChKwgpEQ7AIK1OLpZ934EGbQUcVWHczs:Hc8/xppxpEQ7lLpfZchHcg
TLSHT16B6309417A0F0507F2A65EB0122FA3D2E31DAEC29574916F231AB74B3460B79256FBDC
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
MD50A36E3B18FCFE7CB386E6892C2E929F9
PackageArchppc
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.
PackageMaintainerKoji
PackageNamepl-odbc
PackageRelease4.fc18
PackageVersion6.0.2
SHA-1D627DC6F058CCDF444F61DE069FB4C80AF03DD36
SHA-256CE58AA3DC0A4E4AF6BC63728B4B860D86B4904DDAC299F3CC49252056F5A4267