Result for C9DED467BFDC2E7022F8C08AC7E880EEAFD3E2D8

Query result

Key Value
FileName./usr/lib/.build-id/76/88e4f2705e4a17ef6727d4e6ae80324747c822
FileSize62
MD5C9A7261618BB509C5516A786137081DF
SHA-1C9DED467BFDC2E7022F8C08AC7E880EEAFD3E2D8
SHA-256C2D0E01E2A53780AF14BFB22E8BB98C26642F6328B029D387ACB489B78450D49
SSDEEP3:gCD/bj6pJdtn8RjiKn:X/bWnop
TLSHT174A0027446F96314B9613DE12E141D1837616D41B374DF91C49E427B82544554240C64
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
MD568AA03E18EE0C1AF206EEDC91DC85FA7
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
PackageRelease3.fc32
PackageVersion8.0.3
SHA-129740C0A3A93BCFBEC7C1822DE0782DC536EB2BF
SHA-256C89533CE305C5280DB0E0E3099A87AFAFC9E91EA49A42ADFB1FE8B268EFA37DF