My memory too ;) - Left middle of 2017, here is some article that mentions it - https://www.nextplatform.com/2019/01/15/spanning-the-database-world-with-google/

My memory too ;) - Left middle of 2017, here is some article that mentions it - https://www.nextplatform.com/2019/01/15/spanning-the-database-world-with-google/ https://www.nextplatform.com/2019/01/15/spanning-the-databas... also some bare mention here - https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/46103.pdf https://static.googleusercontent.com/media/research.google.c... "... The effort to standardize our own implementations both covers gaps in the SQL standard where details are unclear or left to the implementation and covers our own Google specific extensions. Before defining our own SQL dialect, we did consider other options. Using the front end of an open-source SQL processing system, such as Postgres, would have accomplished several of the same goals including filling the gaps left by the SQL standard and ensuring uniform syntax/semantics across our systems. We ruled out this approach because internal systems at Google make heavy use of Protocol Buffers in their applications, and we wanted Protocol Buffer message and enum types to be first class types in our SQL language"