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

Urlrefactor #113

Merged
merged 12 commits into from
Mar 1, 2017
Merged

Urlrefactor #113

merged 12 commits into from
Mar 1, 2017

Conversation

jnturton
Copy link
Contributor

@jnturton jnturton commented Feb 13, 2017

  • Call node-mssql using URL instead of options object
  • Encapsulate URL surgery in single class db-connection-config.js
  • Update test suite
  • Connection test run against: SQL Server, Postgres, MySQL

@lukemurray
Copy link
Owner

Awesome, thanks for this.

@lukemurray lukemurray merged commit b3a6e54 into lukemurray:master Mar 1, 2017
@jnturton
Copy link
Contributor Author

jnturton commented Mar 1, 2017

If you can hold off on a new release for a little bit I should be able to sort out #34 too. As well as getting sql-server-manager.js to keep a single connection object alive between queries (currently it's a new connection every query) so that SQL Server session objects like #temp tables can be used across queries.

@lukemurray
Copy link
Owner

Sorry already went out. Both of those things would be great though. It's easy to push another release when they are ready.

Is the second one (keeping a single connection) a regression from this PR? Or did it do that previously? I forget the implementation and don't have access to MS SQL now.

@jnturton
Copy link
Contributor Author

jnturton commented Mar 1, 2017 via email

@jnturton jnturton deleted the urlrefactor branch March 1, 2017 11:11
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

Successfully merging this pull request may close these issues.

None yet

2 participants