CC v5 returns error:0 even after the query was fixed

Hi Bob

I am using CC v5 to pull data out of the table. I noticed if I made error in say the syntax in the Column List of Sortable, CC would return Error:0 along w/ the SQL statement. This is an expected behavior, however, CC would persist this error message after the error has been corrected, even after the cache has been cleared, etc. For example, I have a working connection that broke after I added erroneous syntax in the Sortable. However, no matter what I tried, it won't stop showing the Error:0 message. I created another connection, and the same pattern repeated itself again. So far, it seems that the only way to move forward is to create a new connection with the settings copied over from the previous connection. This become extremely tedious and punishing. Has anyone experienced/reported something similar? And I think this is a behavior you can replicate easily on your end….

Thank you for your help.

SH

In CC5 you have to delete the cache after every change.

Rob

Hi SH,

I've not seen this before. Are you running on LocalHost? I Googled and found this StackOverFlow answer suggests that Error0 indicates that the MySQL service needs to be re-started. Does that help at all?

Bob