Result for B3BFC18020A71A163DDECDA3976011E55E3D6276

Query result

Key Value
FileName./usr/lib/.build-id/84/da9ec66746780d3ebe1d87d632b72f4ac216fc
FileSize61
MD5ADE162734AE43752FEE88D2B5D0F9B9B
SHA-1B3BFC18020A71A163DDECDA3976011E55E3D6276
SHA-2566BCF6AD527889064BCA9A93EF077C45445AE0E806365BF6150957FB7ECF31A1F
SSDEEP3:gCD/bj4QEK76XRjiKn:X/bUQj4p
TLSHT1DFA0026546B8B21579753DE13E181C4837614D50B3749F51C05E40BB82551594241C79
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
MD5A239F50099B277156BF30CF3E353B752
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
PackageRelease1.fc34
PackageVersion8.2.4
SHA-12892DC040A98EE0FC2A1C3D300B0B1AB33B03F1D
SHA-2564A01CD309ED92B6BCBB471DAA3D8865C094435A1AAC6F1E8B6DF2A699C0439A3