Re: Issue with updates to Cloud SQL instances using API

Quick update:

The fix has been pushed to production. Instance setting changes performed via the API do not default the activation policy to "always on" anymore.

On Monday, December 2, 2013 9:52:30 AM UTC-8, Joe Faith wrote:

Hi

A problem has been reported with updating Cloud SQL instances using the API.

If the 'activation policy' field is not explicitly defined, then the value defaults to 'always on' rather than 'on demand'. This can result in instances being kept active for longer than expected.

We expect this issue to be fixed by December 6th.

In the meantime, please specify the activation policy when updating instances via the API, and contact google-cloud-sql-discuss@ if you have any further questions.

Note that updates to instances from the Cloud console are not affected by this issue.

J

--
Joe Faith | Product Manager | Google Cloud

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-announce+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Moving Cloud SQL support to Stack Overflow

Dear Cloud SQL Users

In order to ensure that more users can get more help with their Cloud SQL databases, we will be moving our support from this email group to Stack Overflow. We're already monitoring the 'google-cloud-sql' tag and will provide the same great level of support and help we hope we've provided in this group.

• If you have questions regarding your account, billing, Terms Of Service, or other administration questions, please email cloud-sql@google.com

• To continue receive announcements about Google Cloud SQL, join the google-cloud-sql-announce group. Subscribe via email: google-cloud-sql-announce+subscribe@googlegroups.com.

• And if you need more comprehensive support then Google Cloud Platform Support Packages provide a range of customized premium support packages

See you all on SO!

j

--
Joe Faith | Product Manager | Google Cloud

--
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/CAHNz2%3D8EnNzZg9h%2BoNfv-fQFuN5ykZLXUUFZbnADHpZEqTr78w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Number of instances increase without control and reach max "quota" without being able to to anything.

One thing I forgot to mention: you can use the 'KILL ...' command [1] to terminate a particular connection.

[1] http://dev.mysql.com/doc/refman/5.5/en/kill.html

-- Razvan ME

On Tue, Dec 3, 2013 at 7:15 AM, Razvan Musaloiu-E. <razvanm@google.com> wrote:

A Cloud SQL instance stays up if there is traffic and that includes idle connections over IP. I currently see the instance associated with 853102160359 having two connections over IP. Note: you can see the active connections by connecting with mysql client and issuing 'SHOW PROCESSLIST' [1]. You can also force the instance to stop using the 'Restart' button from Cloud Console.

[1] http://dev.mysql.com/doc/refman/5.5/en/show-processlist.html

-- Razvan ME

On Tue, Dec 3, 2013 at 1:03 AM, bb <brice@hypecal.com> wrote:

Hi,

we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.

There is probably something wrong in our configuration but I don't know how to check it.

The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.

Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 

If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks

 ,

Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg3v7KStyi_XdrKqpmbLe-KWgtB7m1XGcwkF6ST75Mmamw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Number of instances increase without control and reach max "quota" without being able to to anything.

A Cloud SQL instance stays up if there is traffic and that includes idle connections over IP. I currently see the instance associated with 853102160359 having two connections over IP. Note: you can see the active connections by connecting with mysql client and issuing 'SHOW PROCESSLIST' [1]. You can also force the instance to stop using the 'Restart' button from Cloud Console.

[1] http://dev.mysql.com/doc/refman/5.5/en/show-processlist.html

-- Razvan ME

On Tue, Dec 3, 2013 at 1:03 AM, bb <brice@hypecal.com> wrote:

Hi,

we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.

There is probably something wrong in our configuration but I don't know how to check it.

The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.

Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 

If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks

 ,

Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg14L%3DOoyE%2BgurqYT%3DK%3DccyWbcnoT%3Ds_nxyK1UtCJoBfWg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Number of instances increase without control and reach max "quota" without being able to to anything.

Hi,

we have an application in GAE/CloudSQL Number: 853102160359

I don't understand the price it cost daily.

The number of instances required for almost 0 process is not reasonable.

There is probably something wrong in our configuration but I don't know how to check it.

The actual settings makes Google Interface more than thousand times more expensive than the OVH private server that we use before.

To have an idea to compare with Google, a unique private server cost $750/year with the same results in therms of page rendering and speed in the US, France and Spain at the same time.

Where Google cost $20/day in Cloud SQL and between $15 and $80 per day! in GAE.

In this beta website, we are talking about less than 100 Unique Visitor per day...

In my humble opinion, or our configuration is wrong and we can improve our settings to get competitive prices with other server providers, or your prices or conf. are not optimized to match with the real client consuming.

(a fare target for your KPIs could be an average cost per client GAE+Cloud SQL to $10/day). 

If we want to use Google Servers it's for scalability, but scalability doesn't mean using a Porche for a bicycle race.

Can you have a look to the project GAE project 853102160359 and tell me if something goes wrong ?

Thanks

 ,

Brice

--
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/94aa7b6f-dd5e-4a30-a260-462469886394%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Issue with updates to Cloud SQL instances using API

Hi

A problem has been reported with updating Cloud SQL instances using the API.

If the 'activation policy' field is not explicitly defined, then the value defaults to 'always on' rather than 'on demand'. This can result in instances being kept active for longer than expected.

We expect this issue to be fixed by December 6th.

In the meantime, please specify the activation policy when updating instances via the API, and contact google-cloud-sql-discuss@ if you have any further questions.

Note that updates to instances from the Cloud console are not affected by this issue.

J

--
Joe Faith | Product Manager | Google Cloud

--
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/CAHNz2%3D-D6yCx1_z16p6rsBAgWVEEA8S9C%3DsnNm3XZFWGQVe_GQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Cannot create new instance (billing not enabled)

Same problem. Project number: 167339732705

Thanks for the help.

On Sunday, November 4, 2012 4:33:59 PM UTC-5, Mike Drummond wrote:

I'm receiving the following error when attempting to create a new instance: "you cannot create new instances because billing is disabled".
I can confirm billing is enabled.
Project number: 411892037600

--
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/81455216-c9bf-4f13-854b-3a00d005a4bb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

I see that you mention additional new connection is acked by server but statement does not return result. This hints me that it likely to a MySQL level issue with locks etc. Please follow Razvan's instruction for debugging the issue.

On Nov 24, 2013 10:07 AM, "Razvan Musaloiu-E." <razvanm@google.com> wrote:

Things are not quite clear yet for me. Can you please do the following test:

• establish two connections (A and B)
• on connection A do the DROP DATABASE
• on connection B do an SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS

-- Razvan ME

On Sat, Nov 23, 2013 at 6:16 PM, <david.nielson@o3apps.com> wrote:

Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
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/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CABeVsY%2BCjtc0JzVeH6wadbFAL%2BmniNiw%2BL1x_O7t6Grp%2B%3DTQ%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Lost Instance

I undeleted the instance. You are keep loosing it because it belong to a project that was deleted. Please dump the data an import it in an instance in an active project.

-- Razvan ME

On Fri, Nov 29, 2013 at 4:40 PM, Bingxin Liu <liubx1988@gmail.com> wrote:

My instance abtpj-2013:abt is lost again, can you help me to restore again? I don't know why?

Thanks

--
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/ae2b16e1-a315-41a0-b413-24f316f57901%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg0TDShhLMrkK7q7HJsD82oJbezW-w%3DP_U_i-FQtTuct9w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Lost Instance

My instance abtpj-2013:abt is lost again, can you help me to restore again? I don't know why?

Thanks

--
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/ae2b16e1-a315-41a0-b413-24f316f57901%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Is it possible to use Cloud SQL for free.

Hello Alan,

I faced the same problem. I submitted my app but it isn't working. I tried connecting to a MySQL Database on another server remotely. It works offline and it is broken online. I'm still struggling to get a credit card to get it working.

http://gcdc2013-timemate.appspot.com/

On Monday, November 4, 2013 4:26:12 PM UTC+1, Alan Museljic wrote:

I'd like to enter the #gcdc2013 competition. I've developed a php framework and an application built on it that I'd like to submit.
The application uses database and it works great on my localhost env.

I thought app engine is free and it comes with a free database but now I find out that I need to use Cloud SQL and that

it requires a billing enabled which requires a credit card information which I unfortunately do not have.

Is there any other way to use database in app engine with php for free without enabling the billing info?

--
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/96d7b55e-05d9-4153-9f80-94fdc52ec84b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Connection id no longer valid.

How to keep track of the validity of the connection. The use of method "emfInstance.isOpen()" can check the connection is in open state but still get this exception

Caused by: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Invalid connection id.

Is there any method like "emfInstance.isValid()" so that we can reuse the "EntityManagerFactory" untill its still valid and open.

or would you suggest to create a new EMF instance for every db transaction.

Please help!

Aadhaar

On Saturday, February 23, 2013 7:14:43 AM UTC+5:30, Razvan Musaloiu-E. wrote:

Do you keep a connection open without using it for > 15 minutes? The per use instances have a timeout of 15 minutes. After the timeout the old connections will be invalid. I don't see any abnormal terminations for your instance.

-- Razvan ME

On Fri, Feb 22, 2013 at 5:24 PM, Fábio Peruchi <fhpe...@ciandt.com> wrote:

I'm running my queries from a linux machine (Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011).

My instance name is cit-sas-rederef-dev:pgs. My database name is pgs.

On Fri, Feb 22, 2013 at 10:15 PM, Razvan Musaloiu-E. <raz...@google.com> wrote:

Where do you issues the queries from? Can you tell us the instance name? Feel free to contact me directly to write to sql-...@google.com.

-- Razvan ME

On Fri, Feb 22, 2013 at 5:11 PM, Fábio Peruchi <fhpe...@ciandt.com> wrote:

Hi!

I'm running a batch process that execute several insert and delete statements on Cloud SQL. After some hours the process are running I'm getting this error:

Caused by: com.google.cloud.sql.jdbc.internal.SQLUnknownConnectionIdException: Connection id no longer valid.

at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlExceptionForApplicationError(Exceptions.java:195)

at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlException(Exceptions.java:211)

at com.google.cloud.sql.jdbc.internal.SqlProtoClient.check(SqlProtoClient.java:198)

at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:87)

at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:76)

at com.google.cloud.sql.jdbc.Connection.executeSql(Connection.java:528)

at com.google.cloud.sql.jdbc.PreparedStatement.executeSqlImpl(PreparedStatement.java:141)

at com.google.cloud.sql.jdbc.Statement.executeImpl(Statement.java:154)

at com.google.cloud.sql.jdbc.Statement.executeUpdateImpl(Statement.java:341)

at com.google.cloud.sql.jdbc.Statement.executeUpdate(Statement.java:336)

at com.google.cloud.sql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:134)

Can you help me?

Kind regards.

Fábio Peruchi

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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/2295ad7f-989e-45e5-a847-e8ba02a8bc2e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?

For partial update, use the patch method - https://developers.google.com/cloud-sql/docs/admin-api/v1beta3/instances/patch

On Tue, Nov 26, 2013 at 7:55 PM, Razvan Musaloiu-E. <razvanm@google.com> wrote:

The inactivity timeout for Package Plan is 12 hours. Using the API you can also set the activationPolicy to ALWAYS to prevent the instance to do down [1]. Note that for an instance that is on most of the time a Package Plan is cheaper.

[1] https://developers.google.com/cloud-sql/docs/admin-api/v1beta3/instances/update

-- Razvan ME

On Tue, Nov 26, 2013 at 6:16 PM, <brettstaib@gmail.com> wrote:

Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg1_CxKhXsgb9k%2BLoXwPL7_kwGP1bZAooMocP9TMo_MgZA%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
-Sundar

--
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/CABrSwLTaSPVTEVUPQxMKbV4KFc0yp9pEeOMxyJq54eXEMzdhbg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?

The inactivity timeout for Package Plan is 12 hours. Using the API you can also set the activationPolicy to ALWAYS to prevent the instance to do down [1]. Note that for an instance that is on most of the time a Package Plan is cheaper.

[1] https://developers.google.com/cloud-sql/docs/admin-api/v1beta3/instances/update

-- Razvan ME

On Tue, Nov 26, 2013 at 6:16 PM, <brettstaib@gmail.com> wrote:

Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg1_CxKhXsgb9k%2BLoXwPL7_kwGP1bZAooMocP9TMo_MgZA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Will MySQL instance stay up if I change to a the Package Plan rather than the per use plan?

Google states that on the per use plan the MySQL instance is taken down after 15 minutes of inactivity. I'd like to not have the database go down so I'm wondering if it will stay up all the time under the Package Plan? Or is there a way to force it to stay up under the per use plan?

I don't see an option to convert to a Package plan, only change the per-use plan. Am I missing something?

thanks for any input.

--
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/43b92b6b-8087-4e80-8074-70f9f3ccdf03%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Cannot create new instance (billing not enabled)

'm receiving the following error when attempting to create a new instance: "you cannot create new instancesbecausebilling is disabled". can confirm billing is enabled. Project number:  1090661077233

--
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/df260424-7a49-4d1c-9f62-2e17862c631c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: CLOUD

Hi ArunKumar,

If you can describe what specifically you are looking for, we can provide you appropriate pointers. If you are looking at getting started with Cloud SQL, you might find the following video useful.

http://www.youtube.com/watch?v=_kQXgjIfLgo

-Sundar

On Mon, Nov 25, 2013 at 11:35 PM, ArunKumar CM <churiarun@gmail.com> wrote:

If anybody have ppt's on cloud sql plz send me

--
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/8d94d2fb-f35f-4c62-926b-0ec7ccf454e5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
-Sundar

--
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/CABrSwLRdx4WuFDjiJ_WAi8BFdsQ3JHSQ-vODJf73EdR6-KDSRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

CLOUD

If anybody have ppt's on cloud sql plz send me

--
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/8d94d2fb-f35f-4c62-926b-0ec7ccf454e5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

On Nov 23, 2013 10:18 PM, "Gabriel Axel" <guznik@gmail.com> wrote:
>
> I'm sure I don't, and I intend to migrate to AppEngine Datastore eventually. I thought to use Cloud SQL as an intermediate phase, but it seems it would be better to move on to Datastore. Thanks anyway.

Appengine Datastore has a limit of 1mb per entity (and 10mb per transaction - see the bottom of https://developers.google.com/appengine/docs/python/datastore/ ), so I think cloud storage is your best bet here. 

>
>
> On Sunday, November 24, 2013 4:00:50 AM UTC+2, Razvan Musaloiu-E. wrote:
>>
>> One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].
>>
>> [1] https://developers.google.com/cloud-sql/docs/external
>>
>> -- Razvan ME
>>
>>
>> On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guz...@gmail.com> wrote:
>>>
>>> I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?
>>>
>>>
>>> On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:
>>>>
>>>> You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.
>>>>
>>>> -- Razvan ME
>>>>
>>>>
>>>> On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:
>>>>>
>>>>> Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?
>>>>>
>>>>>
>>>>> On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:
>>>>>>
>>>>>> I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).
>>>>>>
>>>>>> -- Razvan ME
>>>>>>
>>>>>>
>>>>>> On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:
>>>>>>>
>>>>>>> I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
>>>>>>> docollabapp:docollab ?
>>>>>>>
>>>>>>> On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I'm trying so set max_allowed_packet by running the following command from the root user:
>>>>>>>> SET GLOBAL max_allowed_packet = 999*1024*1024
>>>>>>>> and I get this error:
>>>>>>>> Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation
>>>>>>>>
>>>>>>>> I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>
>>>>>>> --
>>>>>>> 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/9dcfac85-c808-4c50-9176-feed1390692a%40googlegroups.com.
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>
>>>>>>
>>>>> --
>>>>> 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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%40googlegroups.com.
>>>>>
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>> --
>>> 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/619ba22b-d1f3-4c53-9cab-13255e7f197d%40googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
> --
> 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/4e34fecd-f85b-43d3-8cf9-538fbf046b27%40googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.

--
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/CAOMt%3DViEsnis2zRMxc4j3_mE3yxxnAsLUFmL3dO1K2CyfeXE6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

I'm sure I don't, and I intend to migrate to AppEngine Datastore eventually. I thought to use Cloud SQL as an intermediate phase, but it seems it would be better to move on to Datastore. Thanks anyway.

On Sunday, November 24, 2013 4:00:50 AM UTC+2, Razvan Musaloiu-E. wrote:

One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].

[1] https://developers.google.com/cloud-sql/docs/external

-- Razvan ME

On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guz...@gmail.com> wrote:

I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:

You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME

On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:

Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?

On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:

I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME

On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:

I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:

Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

Thanks.

--
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/9dcfac85-c808-4c50-9176-feed1390692a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/619ba22b-d1f3-4c53-9cab-13255e7f197d%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/4e34fecd-f85b-43d3-8cf9-538fbf046b27%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

Things are not quite clear yet for me. Can you please do the following test:

• establish two connections (A and B)
• on connection A do the DROP DATABASE
• on connection B do an SHOW PROCESSLIST and SHOW ENGINE INNODB STATUS

-- Razvan ME

On Sat, Nov 23, 2013 at 6:16 PM, <david.nielson@o3apps.com> wrote:

Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
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/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg2guOuSGxwHnEFDG2e-2-0oqpZcYLB-AjOOuCdXN8Cz2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "drop database" Command Kills CloudSQL Instance

Razvan,

Here is some additional detail:

Instance hangs = From the cmd line the command is given and simply never returns. While the server is "hanging" on the drop db request new connections are acknowledged by the server, however, additional statements/commands submitted will not return a result. From the MySQL Workbench application the command is given and after a period of time the workbench application stops functioning.

After the instance is restarted via the Google Cloud portal the database will successfully drop but if another drop command is given the issue resurfaces again.

Thanks for your time.

--
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/1eba11a4-9b48-4235-a3f4-63ae25f70bb2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

One row with a column of 400M. Wow! Are you sure you really want that? :-) One workaround I would suggest is to use the IP connectivity [1].

[1] https://developers.google.com/cloud-sql/docs/external

-- Razvan ME

On Fri, Nov 22, 2013 at 12:03 AM, Gabriel Axel <guznik@gmail.com> wrote:

I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:

You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME

On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:

Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?

On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:

I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME

On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:

I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:

Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

Thanks.

--
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/9dcfac85-c808-4c50-9176-feed1390692a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/619ba22b-d1f3-4c53-9cab-13255e7f197d%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg2WLXJAs%3DOmNWXx_Wdt%3DASVS8pWm78%3D-ZY08dqcMsGX-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Setting max_allowed_packet

I would not recommend using --extended-insert=false because that will produce a much more inefficient dump.

-- Razvan ME

On Fri, Nov 22, 2013 at 11:00 PM, Gabriel Axel <guznik@gmail.com> wrote:

I tried mydqldump with extended-insert=false to produce shorter insert statements, and with this the import has been running for 12 hours and is still running. For all that time the storage in used showed in the console is 2.18G. Can you please check if anything is wrong with the instance?

On Friday, November 22, 2013 10:03:00 AM UTC+2, Gabriel Axel wrote:

I currently have longtext fields of up to 400M, so mysqldump fails if I use lower max-allowed-packet value. Any way to overcome this?

On Friday, November 22, 2013 12:53:18 AM UTC+2, Razvan Musaloiu-E. wrote:

You hit the 16M limit for a line length. Can you chop that in smaller pieces? If you use a mysqldump --max-allowed-packet=16777216 things should work fine.

-- Razvan ME

On Thu, Nov 21, 2013 at 2:32 PM, Gabriel Axel <guz...@gmail.com> wrote:

Thanks. I started importing my database, the import ran for two and a half hours and then failed. I tried to repeat it and the same happened. I used mysqldump with the flags as described in the instructions, gzipped it and uploaded to gs://docollab-helper/dump.sql.gz . What went wrong?

On Thursday, November 21, 2013 5:48:54 PM UTC+2, Razvan Musaloiu-E. wrote:

I manually set the max_allowed_packet to 1073741824 for docollabapp:docollab. That's the max (reference).

-- Razvan ME

On Thu, Nov 21, 2013 at 7:35 AM, Gabriel Axel <guz...@gmail.com> wrote:

I understand that you removed the super privilege entirely. Can you please either enable it or set max_allowed_packet=999M on my instance
docollabapp:docollab ?

On Thursday, November 21, 2013 10:22:11 AM UTC+2, Gabriel Axel wrote:

Hello,

I'm trying so set max_allowed_packet by running the following command from the root user:
SET GLOBAL max_allowed_packet = 999*1024*1024
and I get this error:
Error Code: 1227. Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I need this because my database stores longtext fields which cause import and insert/updates to fail without increasing max_allowed_packet.

Thanks.

--
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/9dcfac85-c808-4c50-9176-feed1390692a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/6e64f31f-bfdf-47e2-bacf-ce8b80dbe88a%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/f0e2b21e-47bf-4857-95e1-01130eb3675e%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BUvTg19vRJw04-0CzepeCZCb9t%3DTVsLkdy30rPzC4hm3%3DgMEA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.