No, this is as designed.
The new version of databridge has built in Cross Site Scripting prevention for security. You have to manually disable it when you have html, javascript, or direct references to code in your column.
You can disable it globally by updating your rsobj.php file. You can disable it on the recordset level, or you can disable it in individual getColumnVal() references. The example I gave you disables it in the getColumnVal() method by appending the "false" parameter at the end.
I think it is best to have the Cross Site Scripting enabled by default, so people will have to get used to making the change in the code in one of the three locations in order to get around it when necessary.