Say Hello To GoogleSQL (nerds.xyz) 32
BrianFagioli writes: Google has quietly retired the ZetaSQL name and rebranded its open source SQL analysis and parsing project as GoogleSQL. This is not a technical change but a naming cleanup meant to align the open source code with the SQL dialect already used across Google products like BigQuery and Spanner. Internally, Google has long called the dialect GoogleSQL, even while the open source project lived under a different name.
By unifying everything under GoogleSQL, Google says it wants to reduce confusion and make it clearer that the same SQL foundation is shared across its cloud services and open source tooling. The code, features, and team remain unchanged. Only the name is different. GoogleSQL is now the single label Google wants developers to recognize and use going forward.
By unifying everything under GoogleSQL, Google says it wants to reduce confusion and make it clearer that the same SQL foundation is shared across its cloud services and open source tooling. The code, features, and team remain unchanged. Only the name is different. GoogleSQL is now the single label Google wants developers to recognize and use going forward.
As you wish (Score:2)
SELECT "GoogleSQL" AS "Hello";
I guess.
Re: (Score:3)
Re: (Score:2)
I'd have used no quotes at all.
Re: As you wish (Score:2)
Re: (Score:2)
Given the title says to "say hello to GoogleSQL", it's obvious their intent was to interact with it via the DBI module in perl.
Sign of impending doom? (Score:2)
Given how keen Alphabet is to kill off something that doesn't instantly earn billions, is this a hint this project is also at death's door?
Re: Sign of impending doom? (Score:5, Interesting)
Re: (Score:3)
Re: (Score:2)
Exactly my first thought too.
Re: (Score:2)
Well, it was kind of informative to me since I barely use anything google. I am not talking about the name change although, just the fact that it exists and that it's used internally.
Another Google fad project (Score:5, Insightful)
You'll regret falling for a Google fad project: https://killedbygoogle.com/
Re: (Score:2)
It's not gone. Clearly you have never actually used it, or you would know that. Nice troll.
Re: (Score:2)
It's just a gag about the usual sequence of events from Google on a project, and maybe a South Park reference...
Re: (Score:2)
Re: Another Google fad project (Score:3)
It is not gone? https://github.com/google/goog... [github.com]
Re: (Score:2)
Soon in the news (Score:5, Insightful)
Soon: Say Goodbye to GoogleSQL
Why not use ChatGPT? (Score:2)
Just give normal language instructions and let ChatGPT create the needed SQL
Seems like it was made for that job.
But why? (Score:3)
Re: (Score:3)
There are lots of SQL already floating out there. Why did Google feel the need to add yet another to the mix? Does GoogleSQL genuinely offer benefits over others out there, or is it just not-invented-here syndrome?
I know nothing about GoogleSQL/ZetaSQL, but its description from its GitHub page [github.com] describes it as an, "Analyzer Framework for SQL."
Furthermore, if you read TFS, you'd know this is not a new project, merely just a new name. There are easily references to its previous name (ZetaSQL) dating back beyond 2020 (a few that I quickly found dating back to 2014), so they're not, "add[ing] yet another to the mix."
Re: But why? (Score:2)
Itâ(TM)s the SQL dialect of all internal and cloud product databases in the company. They open sourced it to give BigQuery users the ability to run the parser by themselves for validations, etc. without using the engine. Itâ(TM)s not going anywhere.
Re: (Score:2)
It's the SQL dialect of all internal and cloud product databases in the company. They open sourced it to give BigQuery users the ability to run the parser by themselves for validations, etc. without using the engine. It's not going anywhere.
That part I get. My deeper question is: why does this dialect need to exist at all? Does it accomplish something that other, pre-existing dialects did not (could not) accomplish?
Re: (Score:3)
There are lots of SQL already floating out there. Why did Google feel the need to add yet another to the mix? Does GoogleSQL genuinely offer benefits over others out there, or is it just not-invented-here syndrome?
On the good days they do it to add some nice-to-have features (one dialect I'm aware of added a keyword that says "yeah, just assume I put all those fields in the GROUP by clause", which IMO should just be in the main spec). But it definitely is also a play for vendor lock-in. (Oh, you used our nice extensions? Welp, guess you're stuck with us unless you want to rewrite all your queries sucker!)
Clarifying Shitty Article (Score:4, Informative)
A Slashdot article that is a blog post about a blog post. For fucks sake Slashdot!
To clarify; GoogleSQL(nee ZetaSQL) is a higher level SQL language for querying across a wide range of different SQL and SQL like systems.
GoogleSQL is not a database.
The link that TFA should have included is https://github.com/google/goog... [github.com]
I'm still confused (Score:2)
They should have named it AlphabetSQL, right?
Re: (Score:2)
sequalphabet sounds better to me.
Nah (Score:1)
Meanwhile at Google (Score:2)
DROP DATABASE ZetaSQL;
-- aw, fsck it, we all know it's going to end like this anyway.
DROP DATABASE GoogleSQL;