-
Notifications
You must be signed in to change notification settings - Fork 77
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
CockroachDB #136
Comments
By adding an
Looks like the backendkeydata frame data isn't actually really used by crystal-pg, and it's optional according to the spec, so it should be possible just to ignore if the frame isn't sent. I just tested commenting out these lines and it connected to cockroach and worked just fine. |
@RX14 , mind telling where one adds the inspect_with_backtrace? Still seeing issues even with the code in PQ connect disabled. |
@Wulfklaue add it here: https://github.com/will/crystal-pg/blob/master/src/pg/connection.cr#L16 before the raise rescue ex
ex.inspect_with_backtrace(STDERR) |
Found the issue...
Thanks for the code.
Had already written it but was not able figure out why i was not getting the backtrace. Forgot the "STDERR". 👎 Note: Manual really is not useful on this part. Its working perfectly now. Thanks for the help. |
@Wulfklaue yeah just leave off sslmode, the default for crystal-pg is to try with and fall back to without ssl. There's no mode to force disable ssl at the client-side (you can still turn it off at the server) currently. Should be easy to add though (simple patch). |
Testing the Crystal PG driver with CockroachDB ( uses a PostgreSQL compatible interface ).
After a series of tests, it always comes down to:
Different combination keep resulting in the same error.
Note: compiled under Windows WSL but run on a online server that has CockroachDB.
Same tests under PHP and Go results in active and working connections.
Go:
PHP:
Any clue as what may be wrong?
The text was updated successfully, but these errors were encountered: