Does this extend to TCP from Workers? I.e. via the Socket API or similar?
Does this extend to TCP from Workers? I.e. via the Socket API or similar?
MTo be clear, Hyperdrive will build a lot of this in — but at some point you need to give us a way to get to that private resource, which has to be Tunnel or Magic WAN (IPSec, GRE, etc)
MNot yet.
SI have been waiting for this for a long time. Excellent Job
KDoes your connection string start with
postgres://?K(or
postgresql://)KIf you do
new URL(yourConnectionString).protocol in Node, what do you get?KKThe note about 3.8.0 doesn't look right either, Hyperdrive was added in 3.10.0.
KMight be another one to cover in your PR? @alex.robinson
UI mean always being warm would obviously be super nice but I think what matters more at least on the hobby project side is not paying for idle usage. For an actual business use though I do think even paying to keep connection always warm to reduce times is ideal
SWhat if we can configure the idle timeout?
MIn practice most upstream databases will drop the idle connection - “always” may lead people to think we can avoid that.
Dreally excited to play with hyperdrive 
Does it have any usability with rust workers? (ping plz)
Does it have any usability with rust workers? (ping plz)
MThis should work with a Hyperdrive connection string: https://github.com/cloudflare/workers-rs/tree/main/examples/tokio-postgres
- we haven't fully tested, but LMK it does / does not.
KYou'd likely have to use https://docs.rs/worker/latest/worker/struct.Env.html#method.get_binding to access the Hyperdrive binding (for the connection string) as well - but it should be easy enough
SIf i have smart placement enabled, does it work with hyperdrive?
SYeah, smart placement will help minimize the latency in application that makes multiple queries to the database
Pcan hyperdrive be bound to pages?
JSo I have a project that uses Neon for a Postgres DB. My worker currently uses the Neon serverless stuff to connect and works well. I'm also using a bunch of
I'd love to use Hyperdrive, but it seems like using
Any workaround?
node:buffernode:crypto, etc. stuffs via nodejs_compatI'd love to use Hyperdrive, but it seems like using
pgnode_compatnodejs_compatnode: stuff in my own code.Any workaround?
JI guess I could switch to a cutom build and polyfill all the node libs myself... but that's not great DX. Hopefully this can be improved during beta.
RCan hyperdrive be set up for local development to only be used when I run
wrangler dev