DB Synchro does not update revisions table

[deep64blue]

After adding a field to a database table I used DB Synchro to ensure Dadabik knew about it, although the main table was updated Dadabik did not add the new field to the revisions table. I therefore received the following error when updating a record:-

[08] Error: during query execution.

INSERT INTO `zds_revisions_ret_xxx` (`returnID`,`year`,`preacherID`,`date`,`setting`,`bvenue`,`venue`,`denomination`,`timing`,`visible`,`originalid`,`ID_User`,`location`, dadabik_revision_username, dadabik_revision_date_time, dadabik_revision_operation) SELECT `returnID`,`year`,`preacherID`,`date`,`setting`,`bvenue`,`venue`,`denomination`,`timing`,`visible`,`originalid`,`ID_User`,`location`, 'joe.b', '2023-04-11 14:52:34', 'update' FROM `ret_returns` WHERE `returnID` = '2198'

The DBMS server said: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'location' in 'field list'

After manually adding the field to the returns table evertything worked as expected.

Your current DaDaBIK version​

You are using DaDaBIK version 11.9-Elba platinum, installed on Apr 10, 2023 (installation code: 17299615d85299380a), the latest version of DaDaBIK is 11.9-Elba released on Mar 23, 2023

You are running the latest release of DaDaBIK

In case you want to upgrade to a more powerful edition (from Pro to Enterprise/Platinum, from Enterprise to Platinum) please contact us.

System info​

PHP Version: 8.1.12

mysql version: 10.4.27-MariaDB

Web server: Apache/2.4.54 (Unix) OpenSSL/1.1.1s PHP/8.1.12 mod_perl/2.0.12 Perl/v5.34.1

Client: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36

 

[eugenio]

Hello,
yes, this is expected. I past here as a reference the relevant part of the documentation

• The first time you execute an operation on a table, a dadabik_revision table is created (e.g. for a customers table, a dadabik_revisions_customers table is created). Such revision table reflects the current schema of the main table, if you change the schema of the main table by adding/removing fields, you should manually adjust the schema of the revisions table; if you change the schema of the main table by changing field types, you should also adjust the schema of the revisions table, unless you set $use_text_fields_for_revisions_table = 1.

Best,

 

[deep64blue]

Ah sorry, missed that.