MyDBR 7.7 adds support for PostgreSQL web reporting

MyDBR 7.7 has officially expanded its database compatibility to include PostgreSQL, joining its existing support for MySQL, MariaDB, and Microsoft SQL Server. This update allows the web-based reporting platform to utilize PostgreSQL 12 or later to store both its internal objects and the reporting logic itself.

The platform functions by turning SQL queries into interactive web interfaces, including charts, maps, and tables, without requiring a proprietary query language. By leveraging PostgreSQL's native features, the release provides a streamlined way for developers to publish data-driven portals directly from their existing database structures.

Technical implementation in MyDBR 7.7

• Report Logic: Reports are implemented as PL/pgSQL functions that return one cursor per result set, enabling a single function to construct complex pages containing multiple tables, tabs, and charts.
• Security Integration: The system supports PostgreSQL row-level security by passing the logged-in user to the database or executing reports under specific database roles to enforce data access constraints.
• Operational Controls: Administrators can manage report performance using PostgreSQL's statement_timeout and lock_timeout settings, and can monitor or cancel active reports via a dedicated view.
• Deployment and Requirements: The installation uses a single-transaction script to ensure atomic setup; requirements include PostgreSQL 12+ (14+ recommended), PHP 8.0+ with the pgsql extension, and the citext contrib extension.

Why it matters

This release provides PostgreSQL users with a low-overhead method to deploy business intelligence tools without adopting complex, third-party BI suites. By utilizing native PL/pgSQL and existing database security models, it simplifies the workflow for software engineers needing to provide web-based data access to end-users.