Replaced unindexable CONCAT() with COALESCE(col, '') || ... and refactored dialplan lookup into a CTE with UNION to split destination-based and public-context paths.
CONCAT() is marked as STABLE in PostgreSQL and cannot be used in functional indexes, which forced sequential scans during dialplan lookups. To enable future indexing and improve query optimizability, we replace all CONCAT(a, b, c) calls with (COALESCE(a, '') || COALESCE(b, '') || COALESCE(c, '')), which is functionally equivalent for text columns (treating NULLs as empty) and composed only of IMMUTABLE operations.
Additionally, the query was refactored using a CTE with UNION to decompose a complex top-level OR condition into two independent branches:
1. Dialplans linked to matching destinations.
2. Public dialplans with domain_uuid IS NULL.
This structure allows the planner to optimize each path separately, avoid full-table scans, and leverage primary key lookups efficiently - even without additional indexes.
On a production dataset with 3kk records in v_dialplans, this change reduced dialplans query latency from ~1.5s to ~37ms (40.5x faster), with further gains possible via expression indexes.
- Count the primary key in the SQL statement. Slightly more efficient.
- Updated $dir to $xml_dir
- Add an extra line feed
- Change spaces to tabs
- Remove the method return
* Number translation through exception unable load private property
PHP Fatal error: Uncaught Error: Cannot access private property
Under class defined
```
private $xml;
```
You can't access this properly under private constant
* Fix private property access under class for import()
PHP Fatal error: Uncaught Error: Cannot access private property.
* Vars table v_vars is not propagate table data
Path
```
$xml_file = $_SERVER["DOCUMENT_ROOT"].PROJECT_PATH.'app/switch/resources/conf/vars.xml';
```
Will expand too
```
/usr/share/nginx/fusionpbxapp/switch/resources/conf/vars.xml
```
This causes a failure to provision data into v_vars table for installs with a customized path.
* Update Groundwire template
Voicemail number was not properly named and would not provision. & was needed under wsContactsURL to validate the xml. Opening it gave an error stating:
This page contains the following errors:
error on line 14 at column 119: EntityRef: expecting ';'
Below is a rendering of the page up to the first error.
* Update Groundwire template
Had one too many & under wsContactsUrl line
* Updated Cisco 8000 series templates for KEM button compatibility.
Updated the Cisco 8000 series Key Expansion Module format in the templates to improve editing and provisioning button changes, with the label correctly set to the KEM.
Set max KEM Units to 2 ( Phones Maximum )
- Change the label to Database Schema
- Update the description to say tables, columns and data types
- upgrade.php --schema
- Includes data types by default
- Remove --types from upgrade.php
- command line upgrade --interactive
- Option 2 schema
- Includes data types by default
