Hacker News new | ask | show | jobs
by stingraycharles 2045 days ago
If it's specifically a change Google did, and upstream MySQL still supports this behavior, I'm inclined to agree with you that this is a surprise.

Having said that, it is worth emphasizing that you relied on unsupported / discouraged behavior that "is at your own risk". This isn't just any random feature Google disabled, it's security-related behavior that is discouraged to rely upon by MySQL themselves. This is a big caveat, and is something that I would never recommend anyone to do, especially not when you're planning on outsourcing the management + maintenance of your database.
2 comments
hrktb 2045 days ago
I still find it's an interesting aspect of using GCP. For instance I am no Postgres expert, and while I don't directly do anything fancy with it, I have no guarantee that some library I use doesn't rely on some "at your own risk" feature.

What this means is, while thorough testing can give confidence it works at some point, there is no real guarantee it will continue working even without any changes on our end.

link
simonebrunozzi 2044 days ago
> Having said that, it is worth emphasizing that you relied on unsupported / discouraged behavior that "is at your own risk".

Absolutely this. GCP has no responsibility here.

link