I ran into an issue today where I was trying to add a parameter query.
It was silently getting chopped off after submitting the update, and I couldn't figure out why until I checked the MyDBR application tables - specifically, mydbr_param_queries and its query column.
It's defined as varchar(255).
Is there any harm increasing this in a future build? Or is the preference to create views instead?
MySQL has some odd restrictions on views and creating procedures feels like overkill just for a simple parameter query that has a bunch of UNION ALLs.
PS It would have been nice if the form itself was constrained to 255 characters so the UI makes you aware of the character limitation.