Re: [google-cloud-sql-discuss] Anyway to disable only_full_group_by on 5.7

This is pretty bad, there is no way to set multiple SQL_MODE flags, which can be a huge issue when migrating from 5.5 - not just ONLY_FULL_GROUP_BY but also NO_ZERO_IN_DATE and probably others.

This is a serious bug for anyone importing from a previous MySQL version.  So far it's cost us at least 30 developer hours working through all this and possibly more.  And this isn't the first time I've run into this, it was an issue when we migrated to GCP in my previous company. 

The problem is compounded by the fact that there is no setting to remove ALL the sql_flags, which seems like it would be an easy fix to have 'NONE' as an option....

Chris.

On Thursday, July 14, 2016 at 1:15:28 AM UTC-7, David Newgas wrote:

It's planned, but other properties like bringing second gen to GA probably mean it won't happen for a while (I.e. quarters from now). For now I recommend making sure you find a workaround that works for you, such as session variable.

I do believe that this is valuable and will see if we can find a way to make it happen sooner. If other people are affected by this, feel free to comment on this thread with your use-case so the team can get a sense of how many users need this feature.

David

On Tue, Jul 12, 2016, 11:55 PM Michael Parsons <mic...@touchcare.com> wrote:

David,

I'm hitting the same issue. Any updates?

Michael

On Monday, June 13, 2016 at 11:26:16 AM UTC-4, Thomas Locke wrote:

Hi David , Any update on this bug being resolved. Will the fix be days, weeks or months away do you know ?

Regards,

Thomas

On Friday, 3 June 2016 17:34:35 UTC+1, David Newgas wrote:

Hi,

ONLY_FULL_GROUP_BY isn't actually a database flag, it is one of the possible parameters of the sql_mode database flag. sql_mode is one of the supported flags in Cloud SQL, which means you can change it by editing the instance properties. In order to remove ONLY_FULL_GROUP_BY but leave the other default modes you would need to set sql_mode to STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE(etc). Unfortunately it seems that our validation only allows you to set one mode. This is a bug, which I am reporting now.

In the mean time the best workaround is to use SET SESSION sql_mode='...' at the start of each session to remove the mode.

David

On Fri, Jun 3, 2016 at 6:29 AM, Matt Bourne <matt...@gmail.com> wrote:

It seems like there is no super access and although you can add flags there appears no way to remove default flags like only_full_group_by

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/b977f133-5127-4a54-9fa6-cdc7be6ac465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/c9076355-8d64-47cc-89aa-b02945a56f6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3ac6bfb7-0c02-4ead-a4ff-de055596bd3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.