Result for BE6B19BE65DDB0A389BD47B9E11593502E4D43F3

Query result

Key Value
FileName./usr/lib/.build-id/e6/870d8e6a16e49ad5624e711c6f76707c960f6c
FileSize61
MD5AE36066D81397D0514FF89AEC4E018A3
SHA-1BE6B19BE65DDB0A389BD47B9E11593502E4D43F3
SHA-2565DA06F18543FF0744A243A0DE74E464383A2A32F28E8CDC1564A43343FE87299
SSDEEP3:gCD/bj4v6XRjiKn:X/bUUp
TLSHT157A0026542B8B21479757DE12E181C4837614D50F3399F51C05E40BB82551698242C79
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
MD515DD3B51046F3B052D63BE2EDBEE2AD3
PackageArchx86_64
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-13C1B02032C2AD0BD3BC80AFDEDD7CAD0F40E813A
SHA-256B0682CEA522D02DAFA4E02E6214DE64906598746FDD7E46753BEFC00206CFC8A