-
Notifications
You must be signed in to change notification settings - Fork 420
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
fix: be more cautious when setting db id to empty #1725
Conversation
Integration tests failure for 7a2dad4085fea5d47f2ffb491746a4ba13df6f85 |
Integration tests failure for ba9fc66e548e898881dd4340ef02dbacf0664fb6 |
Integration tests success for f87e63b1dafe8afa823a28aa134b629967d3d6f6 |
Integration tests failure for a33a5d3cb3c53b89195c53d820570e828d745510 |
Integration tests failure for edf756f8d8733a5bd6c4a54220fb201a652e2811 |
Integration tests failure for c0b76409e0bdc3ed9e8a96f6c213eb9bb0328ce8 |
Integration tests success for a86176def8f18e9514c4baaab6c1b4c8c7280847 |
Integration tests success for 276c7fddae732882396f1bd84f1da67d7918e6b2 |
fix for #1674
this adds back in the initial scan on database, and only sets the database id to "" if the error is ErrNoRows, and throws exceptions for all else, without setting the id to "". This is the original behavior. Retaining the ListDatabases function which is necessary in case there is more than one match for the given database name.
Also reverted read to use d.Id() instead of custom import function, which really wasn't necessary here anyways.