or at least disable it and confirm that it is/isnt a problem
erughh , I hate inheriting bad work 😒
I agree... I always prefer to create my own bad work from scratch 😄
Does anyone know if it is possible when creating a custom SS SQLSelect to prevent the framework from adding a into the fields, as in “Select , field 1, field 2…“? I am using joins with group by clauses and it is causing me MySQL errors due to the “sql_mode=only_full_group_by” - if I can ditch the * and only select specific fields that should solve the problem.
Is it difficult to upgrade an existing silverstripe project to the latest stable version?
Well, "difficult" is hard to define. It depends on where you're starting from, and what else is in the project (modules, custom code, etc.)