Another Ultorg release, this time simplifying formulas that involve calculations on dates and times, and improving the display of time durations. Also, by popular request: Highlight the current row, to help users maintain sanity when reading very wide tables. (1/2)

End-to-end encryption: The data in perspective definitions, such as column names and selected filter values, is stored on Ultorg's server in encrypted form only. The encryption key is stored in the “hash” portion of the link (#...), which is never exposed to the server. (2/3)

New in Ultorg 2.1.0: You can now quickly share the current perspective (visual database query), by creating a link to it. Links may be opened by other Ultorg users, or used as a way to store queries in company wikis, git repos, or similar. (1/3)

A bonus feature for some very specific use cases: Text cells can now render inline LaTeX math. (Eventually we should add support for more common markup languages...) (5/6)

You can now resize table columns by dragging the edge of their header. Double-click to restore auto-sizing. And, print layouts will repeat table headers on every page. (4/6)

When staging data edits across multiple tables, you can now insert rows under other inserted rows, even when the join is on an auto-generated primary key. Ultorg will work out the dependencies when you commit. (3/6)

The Compile to SQL action now orders and formats its output columns in a more usable manner. Google BigQuery is also now supported as a data source (with all date/time data types, formula functions, Expand JSON Fields etc.). (2/6)

Ultorg 2.0 is released, with several user-requested features! With conditional formats, you can color rows or cells, or "strike through" a row, based on values or an arbitrary formula condition. (1/6)

This release also makes it easier to work with cells containing long text or JSON values. You can press Ctrl/⌘+Enter to see the contents of the currently selected cell in a dedicated text editor, where keys such as Enter and Page Down will not disturb the cell selection. (2/3)

Ultorg 1.9.4: The new "Compile to SQL" action generates a SQL query from the current perspective. The query is similar to those used internally by Ultorg, but has predictable outer column names, and is better suited for use in external applications. (1/3)

Also, the dropdown that appears when editing foreign keys can now be constrained to show only specific, relevant options.

For example, a dropdown showing Cities may be constrained to show only cities from the country that is selected in an adjacent Country field. (2/3)

Ultorg 1.9.2: For simple data edits, Undo now works even after you have committed the edits to the database.

When Undo is invoked for an already-committed data edit, Ultorg creates a new pending edit that would revert the prior change (similar to "git revert") (1/3)

Similar functionality is also available for Google Sheets connections. You can query the data from Ultorg and save changes back to the underlying sheet. (4/5)

DuckDB, as suggested by some users, turned out to be rather easy to support from Ultorg. Its dialect of SQL is reasonably similar to that of PostgreSQL, and it has all the standard data types available (date, time, datetime, integer, numeric, json, uuid...) (5/7)