You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mesteele opened this issue
May 11, 2023
· 4 comments
Assignees
Labels
bugSomething isn't workingDBDatabase IssuesinvalidThis doesn't seem rightLCB-TechDebtIssue exists in Legacy Code Base. We inherited it.ProdObserved in Production Environment.StabilityIssue impacts or is related to App Stability.
Description Deleting selected events works but moving or copying selected events to the archive database causes the screen to come back as incomplete. This issue only happening in PostgreSQL. The process of moving or copying events does complete, but when the page refreshes. It appears it is trying to close the PostgreSQL database and it has already been closed.
The text was updated successfully, but these errors were encountered:
mesteele
changed the title
PostgreSQL Moving or Copying events to Archive database causes error
PostgreSQL Moving or Copying events to Archive database causes issues
May 14, 2023
This is happening under: 1) PHP 5.6.40 - BASE latest Devl for 8 - adodb 5.20.20 - PostgreSQL 15.2
Log for above. php_errors5.log
2) PHP 8.2.6 - BASE latest Devl for 8 - adodb 5.22.5 - PostgreSQL 15.2
Log for above. php_errors8.log
This is not happening under: 3) PHP 5.6.40 - Original 1.4.5 BASE - adodb 5.20.20 - PostgreSQL 15.2
Log for above. php_errors.log
The Original 1.4.5 BASE works either Moving or Deleting events to the Archive PostgreSQL 15.2 database with no issues.
For 1 and 2 above I can go back into the archive database, and the event that I either copied or moved is there. So, it does complete the transfer but the fails to come all the way back to the main BASE page. I am using the same database for all three. I just have to use adodb 5.20.20 for PHP 5.
All I did for each of the above was Delete the PHP error log, list the events, select 1 event and used the move.
FYI: you 'should' be able to run newer versions of ADOdb on PHP 5x up to a certain point. See the wiki page on that.
Most of the results on that page have been verified by Travis-CI runs. Where we don't know, the verified column is marked as No.
That may help you, as you would have the benefits of running on newer ADOdb code.
Either way, I'll need to figure our why we lose the PostgreSQL DB connection after the archive DB action.
This is probably not the cause, however we need to eliminate anything obviously simple.
Are the $db_connect_method settings in your configurations on MySQL & PostgreSQL the same?
For PostgreSQL I change the below from 0 to 1 and the extra tables are installed:
/* Use referential integrity
* 1 : use
* 0 : ignore (not installed)
*
* Note: Only PostgreSQL and MS-SQL Server databases support
* referential integrity. Use the associated
* create_acid_tbls_?_extra.sql script to add this
* functionality to the database.
*
* Referential integrity will greatly improve the
* speed of record deletion, but also slow record
* insertion.
*/
$use_referential_integrity = 1;
NathanGibbs3
changed the title
PostgreSQL Moving or Copying events to Archive database causes issues
PostgreSQL Archive DB transfer issues.
May 30, 2023
bugSomething isn't workingDBDatabase IssuesinvalidThis doesn't seem rightLCB-TechDebtIssue exists in Legacy Code Base. We inherited it.ProdObserved in Production Environment.StabilityIssue impacts or is related to App Stability.
Expected Behavior:
Current Behavior:
php_errors.log
u_ex230511.log
The text was updated successfully, but these errors were encountered: