Parents (Total: 9)

The searched file hash is included in 9 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	98716
MD5	4FEBE916EF9B156B8AFE3F7FAC6594ED
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b2
SHA-1	B7385CC3FF5476C18A52DD660B15F431FA811BFC
SHA-256	86C93588F6B96D8BA881665D68EC8A4DCB3B0F783EFCBCC1D2E35812DF909B94

Key	Value
FileSize	103124
MD5	BA16A02A080F3D9D9A38757312366F82
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	B18C43AD04CB30B974C2781529B199BE11CE8DF1
SHA-256	797F11C8C2C9CD2457D5F3307A8ADB7ACEBC46C1507E922FF7B33A0643AFAF30

Key	Value
FileSize	99488
MD5	5042B2C86342CBE7EB329B4E6F837A6C
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	21F94D177270A370A9D33982AD0870309E2BA1D2
SHA-256	41A8CE6B890A31004E52D11D3B1C4ADD43B0E7A9F1ACC201FC756BB4A3C2EF4E

Key	Value
FileSize	100740
MD5	B5631B6F8E29B32B7E4D62AAEC3B6C23
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	4B94B9341A53E76BCBBFC76F75CADC4BCE9A4B99
SHA-256	D9643112041C469FE4E38A6016E4289F8152BA09F0D9622B0A72413262625CF9

Key	Value
FileSize	99608
MD5	B7E3D3871E3AA94EDA9854CE64A115E1
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	7B596521DD6759B06D25BC0DF4E1DD18A1E4132E
SHA-256	003FD80F6D4A5E091CD5494340E156D7225A5A2A4E75BF2F4BC282B9B37B6D47

Key	Value
FileSize	102132
MD5	0AC65A1A746BE7D8A84A82341D31BF9E
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	D2AE57F0F70C739BD52CAED8482A24C86AC9BF73
SHA-256	F0625DB994F260C7ABDAFB67E1963108A770D090D6E7EFBC64A2D14857281D81

Key	Value
FileSize	96208
MD5	5D7BB62DECF071AAC47D44B84EA0E59C
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	E3C6E3F8A70FDC64FA0610193064D0F102C41029
SHA-256	42967B246BDC5E690A795D3685E9F08148E5C53A305378FE3334A48D13468202

Key	Value
FileSize	106488
MD5	541FBCF288DA55906F63D7CBCAF251A0
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	7788867AE417A19094CCA04B9E322739A38DA412
SHA-256	56EF1F6E84FCB9D852D4EBE4F9EA00963D51A68318766D4BED64AEC2EC248D78

Key	Value
FileSize	97700
MD5	6ACF7F8138EF4131162CDE59BFCC2EB8
PackageDescription	PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.
PackageMaintainer	Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageName	postgresql-13-ogr-fdw
PackageSection	database
PackageVersion	1.1.1-1+b1
SHA-1	762A8E82959E35D2F0335759D858962DCB289F29
SHA-256	ED84AA9FF920D314927F576695528439C800D73943F7ABCB511ED8347B911CCE