Integrity
Keep keys, constraints, and transactions close to the data.
PostgreSQL administration tools are excellent for people who manage databases. They are not the interface that sales, operations, finance, or support teams should use to perform daily work.
PHPRunner and ASPRunner.NET can supply the missing application layer while PostgreSQL remains the system of record. The design goal is controlled business interaction, not a friendlier copy of a database console.
Use PostgreSQL for storage, constraints, queries, and transactions. Give business users a separate web interface organized around records and decisions: what they may see, what they may change, and what must be validated before a change becomes permanent.
Editing a row is a database operation. Approving a request is a business operation that may update several rows, record the decision, notify someone, and prevent later edits. Pages should expose the second kind of operation and keep the underlying implementation behind it.
Keep keys, constraints, and transactions close to the data.
Use views and queries to provide stable datasets for pages and reports.
Use the web layer for user context, permissions, workflow, and presentation.
Authentication answers who the user is. The application must still decide which records that person may view, whether fields are editable, and which actions are available. Define those rules before exposing the first editing page, especially when one database serves several departments or customers.
Both products connect directly to PostgreSQL and build searchable data pages, forms, reports, dashboards, authentication, and role-based access. Developers can use custom SQL and application events when PostgreSQL functions, views, or multi-step workflows need to be integrated into the user experience.