| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(postgis): lift editable database layers past the 50k feature cap (#3272) * fix(postgis): lift editable database layers past the 50k feature cap Editable PostGIS and SQL Server layers reused vector_ops.MAX_FEATURES, the 50,000-feature cap meant for geoprocessing payloads, so any table over 50k rows failed to load with "Table exceeds the 50000-feature limit for editable layers". Give database layers their own cap, 1,000,000 by default and set with GEOLIBRE_DB_MAX_FEATURES on the processing server. Reading a 1.2M-point table takes about ten seconds. The 413 message now names that setting, and for PostGIS points to the read-only vector tiles mode. Fixes #3270 * fix(postgis): join the cap message explicitly and pin the cap in tests Build the 413 detail from its parts instead of relying on a trailing space in the hint, share it with require_features so the write path has one wording, and pin GEOLIBRE_DB_MAX_FEATURES in the PostGIS tests so a value exported in the shell cannot change their results. * fix(postgis): bound the cap to bigint and cover the SQL Server paths Reject GEOLIBRE_DB_MAX_FEATURES values outside the bigint range, since the cap is bound into LIMIT / TOP (?). Add SQL Server read and write-back cap tests, and note the per-read memory cost in the self-hosting docs. | 2 天前 | |
Document bearer auth in OpenAPI (#3225) * Document bearer auth in OpenAPI * Document optional bearer auth in OpenAPI * Test optional auth OpenAPI routes --------- Co-authored-by: Qiusheng Wu <giswqs@gmail.com> | 4 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 天前 | ||
| 4 天前 |