taubes
Member
Hi,
I ran into some issues after upgrading a copy of my main Dadabik application from 9.21 to 9.22. Basically after the update to 9.2.2 I get unexpected "primary_key_table_field = xxx" errors for all tables and views that are still linked somewhere as a "primary_key_table_field" even for not-enabled and uninstalled tables and views. This is 9.22 specific if I switch back 9.21 all is fine again.
The solution seems very elaborate:
- re-enable all not-enabled databases then turn off READ in the permissions for all groups to prevent them showing up in the menu
- find orphaned primary_key_table_field data in tables/views that have been uninstalled.
The main problem is that the error message only references the "primary_key_table_field = xxx" but not the table causing this error. Very elaborate when dealing with deleted tables/views because the only way to find the culprits is search for the tables in the dadabik_forms table or go through all table/views looking for the orphaned primary_key_table_field.
Question:
Is 9.22 more strict regarding orphaned primary_key_table_fields. Is this on purpose? Or am I overlooking a config setting. It was convenient to not-enable databases that were only needed for drop downs instead of setting the permissions for multiple groups. This also reduced the number of tables shown in the permission (I have almost 100 tables and many I only need for drop-downs).
---
You are using DaDaBIK version 9.2.1-Monterosso enterprise ...
You are using DaDaBIK version 9.2.2-Monterosso enterprise ...
PHP Version: 5.6.37
mysql version: 5.7.23
Web server: Apache/2.4.34 (Unix) PHP/5.6.37
Client: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Safari/605.1.15
I ran into some issues after upgrading a copy of my main Dadabik application from 9.21 to 9.22. Basically after the update to 9.2.2 I get unexpected "primary_key_table_field = xxx" errors for all tables and views that are still linked somewhere as a "primary_key_table_field" even for not-enabled and uninstalled tables and views. This is 9.22 specific if I switch back 9.21 all is fine again.
The solution seems very elaborate:
- re-enable all not-enabled databases then turn off READ in the permissions for all groups to prevent them showing up in the menu
- find orphaned primary_key_table_field data in tables/views that have been uninstalled.
The main problem is that the error message only references the "primary_key_table_field = xxx" but not the table causing this error. Very elaborate when dealing with deleted tables/views because the only way to find the culprits is search for the tables in the dadabik_forms table or go through all table/views looking for the orphaned primary_key_table_field.
Question:
Is 9.22 more strict regarding orphaned primary_key_table_fields. Is this on purpose? Or am I overlooking a config setting. It was convenient to not-enable databases that were only needed for drop downs instead of setting the permissions for multiple groups. This also reduced the number of tables shown in the permission (I have almost 100 tables and many I only need for drop-downs).
---
You are using DaDaBIK version 9.2.1-Monterosso enterprise ...
You are using DaDaBIK version 9.2.2-Monterosso enterprise ...
PHP Version: 5.6.37
mysql version: 5.7.23
Web server: Apache/2.4.34 (Unix) PHP/5.6.37
Client: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Safari/605.1.15