-
Notifications
You must be signed in to change notification settings - Fork 0
DSN window implementation #35
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
base: apache-odbc
Are you sure you want to change the base?
Conversation
I am setting the PR to merge into |
ab159f4
to
2779187
Compare
2b39bca
to
96d283b
Compare
c98f368
to
ce4a14e
Compare
96d283b
to
d23e867
Compare
d23e867
to
5e005da
Compare
if (DisplayConnectionWindow(windowParent, config)) { | ||
properties = config.GetProperties(); | ||
} else { | ||
throw DriverException("Connection canceled by user", "HY008"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is HY008 right? That's for query cancellation usually.
Aside from that, I think if the user cancels the connection dialog the driver is supposed to return SQL_NO_DATA or SQL_NEED_DATA rather than an error. Please check this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should log if there's a cancelled dialog though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm you're right, HY008 is what Apache Ignite passed (link) but the spec does say that HY008 is for cancelled queries. And the spec does say that SQL_NO_DATA
should be returned, there seems to be no error message for canceled dialog actually, so I have removed the throw.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And yes driver logging would be useful. However we haven't enabled logging yet (it is planned for milestone 2), so I have added a todo to add log here after it is enabled.
f957577
to
56b3ad0
Compare
56b3ad0
to
95c0c3d
Compare
DSN window implementation developed according to driver guidelines spec