Brandwatch vs ThoughtSpot

AI Updates: 7 New Ways Brandwatch Is Making Our Customers’ Lives Easier

New blog post published Sep 29 detailing seven new AI-driven features and improvements for Brandwatch customers.

Put Your Data to Work with ThoughtSpot in ChatGPT Work

New blog post: 'Put Your Data to Work with ThoughtSpot in ChatGPT Work' (Sep 10, 2026). Also new: '2026 Best Books on AI and Data' (Sep 10, 2026), 'Introducing SpotterCode in Developer Playground' (Sep 9, 2026), 'Trust, Tested: What Consumers Really Think About AI in Retail' (Sep 2, 2026), and 'Employee Recognition: Meet This Quarter's Icon Award Winners' (Sep 1, 2026).

ThoughtSpot Named a 2026 Gartner® Magic Quadrant™ Leader for Analytics and BI Platforms

ThoughtSpot has been recognized as a Leader in the 2026 Gartner Magic Quadrant for Analytics and BI Platforms, with a dedicated report available for download.

Postgres pattern to query row state as of a time

The article presents a Postgres schema pattern for answering point-in-time questions like “what did this row look like at T?” by keeping a history table alongside the main table (SCD Type 4) and using a row-level trigger to mirror INSERT/UPDATE/DELETE operations into that history table. The author contrasts common alternatives — event sourcing, in-place versioning (SCD Type 2), and periodic snapshotting — and provides concrete SQL: history table creation (LIKE ... INCLUDING DEFAULTS), a trigger function that stamps valid_from/valid_to and writes tombstone rows on DELETE, a point-in-time SELECT that picks the version valid at :as_of, and a backfill pattern for pre-install rows. The piece also warns about operational concerns such as schema drift when adding columns and recommends automating schema migration for history tables.

• The article describes using an SCD Type 4 pattern in Postgres: a records_history table that mirrors records plus valid_from, valid_to and operation columns.
• A row-level trigger function mirrors every INSERT, UPDATE and DELETE on records into records_history, stamping valid_from/valid_to and writing tombstones for deletes.
• The point-in-time query uses WHERE valid_from <= :as_of AND (valid_to IS NULL OR valid_to > :as_of) with DISTINCT ON (record_id) and ORDER BY record_id, valid_from DESC to return one row per record as of :as_of.