Local Connection Fails

Scenario

I run pscale connect galaxy --port 3309 locally to connect to my PlanetScale DB
I attempt to connect my T3 app using import { connect } from "@planetscale/database";

Problem

When I use url to connect to my local db connection, it does not use the specified port - instead is uses port 443:

const connection = connect({
  url: "mysql://root@127.0.0.1:3309"
});

When I use host & username to connect to my local db connection, it uses the correct port but it fails with a ERR_SSL_WRONG_VERSION_NUMBER status code

const connection = connect({
  host: "127.0.0.1:3309",
  username: "root"
});

I'd love to be able to use this package instead of prisma for my next project.

Anything that can be done to help here would be greatly appreciated!

This is correct. We don't have an equivalent yet since this driver speaks HTTP and `pscale connect` is mysql. So in this case, it's not a deficit of database-js, just a fundamental difference in protocol. On Apr 9, 2023, at 20:29, Germán Pineda ***@***.***> wrote: Scenario I run pscale connect galaxy --port 3309 locally to connect to my PlanetScale DB I attempt to connect my T3 app using import { connect } from ***@***.***/database"; Problem When I use url to connect to my local db connection, it does not use the specified port - instead is uses port 443: const connection = connect({ url: ***@***.***:3309" }); When I use host & username to connect to my local db connection, it uses the correct port but it fails with a ERR_SSL_WRONG_VERSION_NUMBER status code const connection = connect({ host: "127.0.0.1:3309", username: "root" }); I'd love to be able to use this package instead of prisma for my next project. Anything that can be done to help here would be greatly appreciated! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

@mattrobenolt thanks for the quick response and clarification!
In that case, do you know how I can specify a DB branch in this configuration?

When you create credentials, they're bound to a branch. So you'd just create credentials for the branch you want, and it'll work. Are you observing something differently?

Ah that's my mistake, didn't realize that was the case. Thanks again for your help!

Out of curiosity, are there any future plans to bridge the protocols?

Bride them how? I have some plans. 👀 But curious what you have in mind.

Hmm let me give it some thought and I'll get back to you!

(Maybe unrelated to your issue? Feel free to ignore)

From what I see, the ERR_SSL_WRONG_VERSION_NUMBER error is caused because fetch tries to do some SSL logic here on a non SSL endpoint.

Changing these 2 lines and switching https to http should make it work.

database-js/src/index.ts

Line 203 in 488e48b

    
           const url = new URL('/psdb.v1alpha1.Database/Execute', `https://${this.config.host}`)

database-js/src/index.ts

Line 254 in 488e48b

    
           const url = new URL('/psdb.v1alpha1.Database/CreateSession', `https://${this.config.host}`)