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

Bind shouldn't take references, leave that for a higher-level interface #89

Closed
Abscissa opened this issue Oct 20, 2016 · 1 comment
Closed
Labels

Comments

@Abscissa
Copy link

When using prepared statements, binding the params requires passing variables by reference.

I suspect the original reason for that may have been as a rudimentary ORM-like approach, where you "bind" params to variables once and only once, and then can call execPrepared multiple times, simply changing the values of the already-bound variables between executions of the prepared statement.

I think that usage-pattern has merit, but it should be left to a higher-level interface, built on top of a pass-by-value binding system. Using references/pointers has too many downsides in modern D to be the fundamental basis of this lib's low-level interface.

@Abscissa Abscissa added the api label Oct 20, 2016
@Abscissa
Copy link
Author

Abscissa commented Mar 1, 2017

Fixed in v1.0.0

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

No branches or pull requests

1 participant