Result for A02F470BA512F4B3B242BD4EC51B0A30F9F17FB8

Query result

Key Value
FileName./usr/lib/.build-id/34/8a156196309ef49a223b766f01f8cff9877c6b
FileSize62
MD5ACAFED264BF5676DC6267F0C650EBC0E
SHA-1A02F470BA512F4B3B242BD4EC51B0A30F9F17FB8
SHA-256160C019F9957705BED9EF18A1CA5145A053F24AB7207E26488A551C4520D2921
SSDEEP3:gCD/bj4QEKtn8RjiKn:X/bUQjep
TLSHT1EEA0026446F963157D653DE13E141D1837514D41B3749F81C45E41BB83544554240C69
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
MD5F698A4BE84F854CA32ECC0186B1E7DB2
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
PackageRelease1.fc34
PackageVersion8.2.4
SHA-1B188EED1A526B0DF7310C4DFA721E79751FBF7E2
SHA-256F2B7DE632ED43C14C7BCF926FEB6B1EF8EB5A4CC4816C431099273907A32DB95