Something is happening that keeps causing my connection script to become "corrupted" by the DMXzone Extension, causing all of my dependent data sources to no longer load. I have to upload a "clean" older version every time to restore functionality to my data sets.

I'm working on a site where the data sources are MySQL prepared Views. These Views have already been confirmed to work in PHPmyadmin. And many work fine already within DMXzone Database Connector. But some Views are causing problems with the Database Source Query Builder when trying to run a test on the query.

This is the error I get when trying to test the query. This query runs fine in MySQL though.



When I load this data source in the query builder, the DMXZone extension makes a background change to my connection script, causing ALL of my other dependent data sets to disappear on the pages. It's somehow corrupting the connection script.

Please see this comparison between the working connection script file and the non-working connection script. The changes were added automatically by the DMXZone extension, and this was before I clicked "Run Test" --- these changes were made by your extension when I loaded the data source into query builder!



Here is a closer look at the View in MySQL (the View is named vwProductDetail_Gallery). Again, this works fine within my database client and query builder, but causes issues in DMXzone Database Connector.



It's also causing data bindings for other data sets (many of which work fine) to disappear from the data bindings panel.



I've tried running a test and re-applying all my database connection settings, re-applied all of the data sources, but it's still causing the connection corruption issue, and having issues with some of the views. I can't figure out why.

Hello,
And your connection should be working fine. The Blue code highlighted by you SHOULD be there. It contains the metadata information from your database.

There seems to be a little issue with the way Database Connection file is created.
The default bit field type value is stored in the connection file as:

"b\'0\'" 

Please find and replace it with

"b'0'"

This will fix your issue. We will improve this in the upcoming update.

I have the same issue. Thanks for the fix.

I am having a similar error, but cannot find where the default bit field type value would be...?

Hi Eric,
Please send your connection file to: so i can check what is wrong there.