Posted by dave at 16:58 on Wednesday 26th August 2026[link]
observation: at line 340, a SQLite DML is executed, but no response is shown when $result === false, meaning that the DML was rejected.
The editor cannot protect the operator from updating a field to, let's say, a non-unique value.
It's complicated, because the server is called right back to redisplay the table, which loses any error dialog.
Suggestion: you might decide to show a dialog immediately, with the return of SQLite3::lastErrorMsg, and cancel the redisplay.
Posted by Richard at 20:11 on Wednesday 26th August 2026[link]
Hi,
> It's complicated, because the server is called right back to
> redisplay the table, which loses any error dialog.
>
> Suggestion: you might decide to show a dialog immediately,
> with the return of SQLite3::lastErrorMsg, and cancel the
> redisplay.
There's a facility in there to show an error message that survives across page refreshes so it can be shown when the table is redisplayed assuming that there's a PHP session either started or one can be started.
The editor tries to start one, but you may need to call session_start() in your page before any HTML is sent to the browser.
But anyhow, displaying an error when an update fails should be fine.