spanner
Here are 40 public repositories matching this topic...
Currently, the README.md file lists all tables with their full table comment.
I'm putting a lot of info in some of my table descriptions, including SQL code blocks. These render rather badly in the comment column of the central Tables table, which treats markdown just a little different.
Perhaps the Tables table should only use the first paragraph of each table description.
E.g.
This repo now has awesome code search support at: https://cs.opensource.google/google-cloud-cpp, but there is no support for cross-reference linking. We can enable that, but it requires us to set up a new build that produces the necessary kythe artifacts, and upload them to a GCS bucket, and a few more configuration steps. The details are described in an internal document at: go/google-cloud-cpp:k
Looks like Google recently released a cloud spanner emulator - It's probably worth testing against this locally and then updating our README with instructions on how specifically to use it with this service.
-
Updated
Aug 14, 2017 - Ruby
-
Updated
Jun 24, 2019 - Go
-
Updated
Jun 4, 2020 - Go
What
Package document comment is missing.
It is useful to understand how to use the packages.
-
Updated
May 22, 2020 - Go
-
Updated
Sep 17, 2019 - Java
-
Updated
Mar 28, 2020 - Go
-
Updated
May 18, 2020 - Kotlin
-
Updated
Nov 25, 2019 - Go
-
Updated
Jun 15, 2019 - Go
-
Updated
May 31, 2020 - Go
-
Updated
Aug 7, 2018 - Go
-
Updated
Nov 8, 2019 - Java
-
Updated
May 18, 2020 - Java
-
Updated
Sep 22, 2018 - Go
Improve this page
Add a description, image, and links to the spanner topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the spanner topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
Provide help in CLI for sub-commands
Describe the solution you'd like
Sub-commands help should describe the sub-command's functionality and options available for the sub-command
Describe alternatives you've considered
N/A
Additional context
See: golang-migrate/migrate#370