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

Support an initial sub-set of the extended query message flow #6

Open
KayEss opened this issue Jun 4, 2017 · 0 comments
Open

Support an initial sub-set of the extended query message flow #6

KayEss opened this issue Jun 4, 2017 · 0 comments

Comments

@KayEss
Copy link
Member

KayEss commented Jun 4, 2017

Version 0.1 brought in support for the simple query mechanism. This is actually pretty useful on its own as it already supports essentially anything you can do with Postgres. It does have some drawbacks though, most importantly (for our use case) is that it requires everything to be turned into SQL statements, and this opens issues about things like SQL injection attacks.

Better is to use the extended query message exchange which allows the data to be embedded directly in network packets in a way that doesn't require textual escaping. And Fostgres uses prepared statements anyway, so we need it.

This is a big feature, so to start with I just want to see the basics working so we can use prepared statements for data insertion. It's a bit parochial I know, but at that point this library covers our use cases and I'd be relatively happy to call it "1.0" :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant