1. 

   TJH, Member

   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.

   Thanks,
   Trevor

   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.
2. 

   myDBR Team, Key Master

   If you have a longer parameter query, just make it a procedure instead. Will be easier to maintain also.

   --
   myDBR Team
3. 

   TJH, Member

   Alright, thank you.

   However, it would be nice to restrict the form itself to only 255 characters or provide an alert when submitting more than that.

   Best,
   Trevor
4. 

   myDBR Team, Key Master

   We'll increase the size of the column.

   --
   myDBR Team
5. 

   TJH, Member

   Team,

   Updated to the latest and many thanks for the increasing the length.

   I agree more involved parameter queries should be procedures for ease of maintenance.

   Thanks,
   Trevor

Reply

You must log in to post.