Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sql: add support for HTTP(s) connections #69146

Closed
awoods187 opened this issue Aug 19, 2021 · 5 comments
Closed

sql: add support for HTTP(s) connections #69146

awoods187 opened this issue Aug 19, 2021 · 5 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-server-and-security DB Server & Security T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Comments

@awoods187
Copy link
Contributor

CockroachDB does not support database connections across HTTP(S). All database connections must be made via TCP. This is a tracking issue for adding support for HTTP connections.

We may pursue this in a variety of ways including #69010

@awoods187 awoods187 added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Aug 19, 2021
@blathers-crl blathers-crl bot added the T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) label Aug 19, 2021
@rafiss
Copy link
Collaborator

rafiss commented Sep 17, 2021

Is the intention to support sending SQL commands in an HTTP request body? This issue needs more details in the main description body.

@blathers-crl blathers-crl bot added the T-server-and-security DB Server & Security label Sep 17, 2021
@knz
Copy link
Contributor

knz commented Sep 27, 2021

Is this an issue redundant with the PostGREST project?
cc @nvanbenschoten

Also I don't understand why this is assigned to the server team

@otan
Copy link
Contributor

otan commented Sep 27, 2021

i don't think the tech note really in the docs as a limitation makes sense either?

https://github.com/cockroachdb/docs/pull/11083/files#r717039281

What brought this issue on? It doesn't seem like something we want anyway (or least, not something that should be expected would block someone enough such that i'd classify it as a "limitation" in the docs) and want a third party (e.g. PostgREST) to support it.

@rafiss
Copy link
Collaborator

rafiss commented Sep 27, 2021

@awoods187 Is this referring to something like the Aurora Data API? https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html

I agree that the tech note as written needs to be clarified

@awoods187
Copy link
Contributor Author

We can close this for now give the progress on PostgREST-- I was merely noting that PostgREST is only one way we could solve this need (we could also build our own connection like FaunaDB for example).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-server-and-security DB Server & Security T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Development

No branches or pull requests

4 participants