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 prepared statements #67

Closed
fsateler opened this issue Apr 13, 2012 · 4 comments
Closed

Support prepared statements #67

fsateler opened this issue Apr 13, 2012 · 4 comments

Comments

@fsateler
Copy link
Contributor

Escaping user input is error prone and boring. We should just let the database handle those whenever possible.

@derAndreas
Copy link

Managed to get prepared statements working for mysql adapter and I think this should be easy to implement for postgresql, but before I'll continue I'd like some feedback.

The change is in derAndreas@7c3b408

I wrote some mocha based tests and it seem to work (not tested with real app).

@rainulf
Copy link

rainulf commented Apr 3, 2013

I see that this issue is still opened. Any updates?

@anatoliychakkaev
Copy link
Collaborator

No.

On Thu, Apr 4, 2013 at 1:43 AM, Rainulf Pineda [email protected]:

I see that this issue is still opened. Any updates?


Reply to this email directly or view it on GitHubhttps://github.com//issues/67#issuecomment-15867185
.

@pyramation
Copy link

this seems to be more of an issue for node-mysql, which jugglingdb relies on. I've been talking to Felix over the past few weeks, and we've started a campaign to get this feature: https://www.crowdtilt.com/campaigns/prepared-statements-for-nodemysql

perhaps some of you can help spread the word?

@1602 1602 closed this as completed Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants