|
There's a new build out, 9.0.182.3. It's a hotfix to the prior build but even if the fix is not relevant to your work I still recommend it for everyone because of the new features it has, brought forward from the planned 26 July build. Here are the release notes: Hotfix + Hot new features 9 July 2026: Build 9.0.182.3 is a Cutting Edge Build that is recommended for all users. The following release notes are preliminary information: documentation has yet to be updated. Build 9.0.182.3 delivers a hotfix for a build error reported by expert user rk on the forum: Release 9 .exe and .zip installations for Build 9.0.182.2 accidentally were configured to use Manifold Viewer restrictions on the ability of third party .NET applications to use either the Manifold API or the experimental Manifold ODBC application from outside Manifold. There was no restriction on scripting within Manifold itself or Manifold's own use of ODBC. Build 9.0.182.3 fixes that configuration error and restores full external .NET and ODBC access. In addition to the hotfix, the new build delivers several outstanding new features that speed up rendering and deliver key structural improvements to essential SQL clauses that can reduce query run times dramatically. As always with Cutting Edge builds, users are advised to retain a backup copy of the prior Base builds in case they would like to revert to 182.2 or 182.1. Highlights Occlusion culling between image server layers - Built-in, opaque image server layers automatically cull (no need to render) all built-in image server layers below them in maps. This greatly improves rendering speed when multiple image server layers are ON in a map. Occlusion culling for all below image server layers- Built-in, opaque image server layers automatically cull all layers below them in maps that are within the bounding boxes of the image server layers. This greatly improves rendering speed when multiple layers are below an opaque image server layer: no need to render a complex or slow layer if an image server layer above it hides it. GROUP BY speedup - A major rework of GROUP BY internals in the query engine provides significant (>10x) speed increase in many common cases with welcome (~3x to ~5x) speed increases in most other cases. Some of the work done for GROUP BY increases speed in various other parts of the query engine as well. ORDER BY speedup - The new build provides significant speed increases, both materialized (SELECT ... INTO) and non-materialized use from the Command Window, especially in "narrow" queries with SELECTs involving relatively fewer fields. The effect is still very noticeable and useful in wider queries involving many fields where execution time tends to be dominated by simple moving of data for so many fields (the ORDER BY sorting in such cases is almost instantaneous). Non-materialized ORDER BY is dramatically faster: interactive sorts of large tables in the SQL Command Window using ORDER BY on a field to sort the table now display the first page as fast as or faster than CTRL-clicking a column header to sort the table. Live ORDER BY views - Materialized views (running an ORDER BY query in the Command Window) now are "live" views that are updated against changes in the original table. Do a SELECT * FROM [table] ORDER BY [field] and the results table will appear rapidly, and then if [table] is opened in a different window and any rows are deleted or any fields are edited the results table in the Command Window will be updated when touched. SELECT INTO with ORDER BY - This removes a limitation where ORDER BY could not be used with SELECT INTO constructions. SELECT INTO now works with ORDER BY without throwing error messages. FETCH with SELECT INTO - This removes a limitation where FETCH could not be used with SELECT INTO constructions. SELECT INTO now works with FETCH. In addition, the FETCH stops materializing records after the desired FETCH number, so if a query uses FETCH 1000 on a 14,000,000 record table the query runs instantly as the INTO now stops scanning the source after the 1000th row instead of materializing 14 million rows. That's a dramatic effect especially when a query using FETCH runs with big tables in an SQL Command Window: it is often an over thousandfold speedup with big tables. (Fix) External .NET and ODBC access restored - Release 9 .exe and .zip installations for Build 9.0.182.2 accidentally were configured to use Manifold Viewer restrictions on the ability of third party .NET applications to use either the Manifold API or the experimental Manifold ODBC application from outside Manifold. There was no restriction on scripting within Manifold itself or Manifold's own use of ODBC. Build 9.0.182.3 fixes that configuration error and restores full external .NET and ODBC access. (Fix) No missing points - It has always been possible to set Styles where the symbol for a point is painted a significant distance away from the actual point. However, in prior builds in a map window the symbol might not have been painted if the point's actual location was offscreen even though the symbol paint location would fall onscreen. Rendering logic has been adjusted to deal with such situations. The bug existed long before current builds but was only noticed when slippy pan, by filling in pan margins, made it visible.
|