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

Cannot connect to different instance of the same database without the original database #763

Closed
halcwb opened this issue Apr 1, 2022 · 1 comment

Comments

@halcwb
Copy link

halcwb commented Apr 1, 2022

Describe the bug
Using a compiled library I want to connect to a different instance of the same database. However, the original database does not longer exist. Unfortunately, I cannot login to the new instance of the database, somehow, a connection to the old instance of the database seems to be required.

To Reproduce
Steps to reproduce the behavior:

  1. Compile a library with access to a database.
  2. Move the database to a different server
  3. Try to access the database using the compiled library using an updated connectionstring, i.e. sql.GetDataContext(connstring).

Expected behavior
Code runs using the moved database instance

Note: this should mean that any compiled code isn't transportable or usable in any other situation?

See related problem; #762

@halcwb
Copy link
Author

halcwb commented Apr 14, 2022

Sorry for this, something stupid on my side. Used an old connectionstring in my code (retrieved by an environmental variable).

@halcwb halcwb closed this as completed Apr 14, 2022
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

1 participant