Result for 75F432D836E62DE03B098105E684BF38D0DFFC46

Query result

Key Value
FileName./usr/lib/.build-id/ce/57c9adaf999a528d3e4ca85b4a69a003463dcc
FileSize62
MD5BEC4CB1BC47F1A43943473BCFE3198D3
SHA-175F432D836E62DE03B098105E684BF38D0DFFC46
SHA-25615561B2FA1155B6D8C4D0979A979141FA4026A7D40B22343F29681D9828300C6
SSDEEP3:gCD/bj4hn8RjiKn:X/bUip
TLSHT156A0026442F963147D657DE12E141D1837514D41F3399F81C45E41BB83544658241C69
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
MD5193990696FEDF220E9C26E959B82F2BE
PackageArchaarch64
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
PackageRelease4.fc33
PackageVersion8.2.1
SHA-1BF460B1DE04D6A6C481D91F2A9B2B300381445DD
SHA-25632D026A3E62B8BBDF53BE9246AD7BAB63AAEE3E50F8C1CA06FB71E4E22AAC444