How to get CC6 to recognize newly added database fields

tfetherston 23 Aug, 2018
In an otherwise functional Connection, newly added database fields are simply ignored and omitted; the debug output does not list them in the query or the output.

Deleting the cache used to work in CC5 - am I overlooking something?

Thanks
healyhatman 24 Aug, 2018
Click the "clear cache" button in the CC menu.
tfetherston 24 Aug, 2018
Yes, my second paragraph was not explicit. I did try that, more than once, to no avail.
tfetherston 24 Aug, 2018
Also, just now I have renamed the cache file and re-compiled my Connection. As a result, the cache file was re-created, but the new one did not contain the newly created fields. Afterward, I chose "Clear Cache" in the CC menu and the response was "0 cache files deleted successfully." Then I checked the cache directory, and the file was still there. Am I looking in the right place (JPATH_ROOT/cache)?

Is there some circumstance under which the Clear Cache feature might not work correctly?
healyhatman 24 Aug, 2018
Yeah I don't know sorry all I can suggest is temporarily turning off Joomla caching? Or delete your read data action and redo it
tfetherston 24 Aug, 2018
Thanks --- I've already tried a fresh Read Data; joomla cache has been off from the start. I'll keep hammering on it for now
healyhatman 24 Aug, 2018
What does your read data action look like
tfetherston 24 Aug, 2018
The fresh read data was simply a model name, table selected, no fields specified (i.e. to collect all available fields). It was collecting only the previously existing fields.

My connection is now able to see the new field, and I believe maybe the mysql server was at fault. I only have mysqladmin access, and could not restart mysqld, so I began trying the table maintenance features, like analyze and optimize. I was in full "random button-pushing" mode, so I did not pay attention enough to which thing corrected the problem; it may have been Defragment or Optimize. I don't know how my table could have gotten corrupted just that little enough to hide newly created fields, but after defrag and optimize, manually deleting the *db_tables_info.cache.php file, and re-saving the Connection, the new field decided to make an appearance.

I'm still concerned about the Clear Cache feature, which does not seem to delete any cache files -- it says 0 files deleted, and when I check the JPATH_ROOT/cache directory the database cache file is still there. I'm assuming this is the right cache file location for Chronoconnectivity, because when I deleted the file manually and re-saved the Connection, a new file was created there. I don't see how it could be a file permission issue, since it's able to create a file with no problem.

Thanks for your help -
This topic is locked and no more replies can be posted.