Result for F87751D3C7F44A2075F96F195F650F94A4B2A9D7

Query result

Key Value
FileName./usr/lib/swipl-6.0.2/lib/s390-linux/odbc4pl.so
FileSize51836
MD545B8255DF0FDE1D56DBAD468B422B18A
SHA-1F87751D3C7F44A2075F96F195F650F94A4B2A9D7
SHA-2560A1BD8A1D08ECE291F72C7417962048411D78C2F640980C4E27F332ED0C3F050
SSDEEP768:fchVDErtIWo0tMmvPWYTOHVPLpijk+CrScBEEiUO6Zm:fcDEr+Wo0yYTMBcYRBEEQ6Zm
TLSHT1283306CE6671CB6ACCE9173B897F81C71FB15430991D020F864CF25CB8AB79C8647A68
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
MD53820C0118343F34CA7DF222AD5A56CF3
PackageArchs390
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.fc17
PackageVersion6.0.2
SHA-17836CA5DAF35B3DC8B826696C940872B94DDFDEB
SHA-256E883ABE89547019FDFDF07156CD3D5F800923AD29D56B50B7C9773E280D236C5