-
Notifications
You must be signed in to change notification settings - Fork 103
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
Add enum column support to relational server #3074
Conversation
Result of fdb-record-layer-pr on Linux CentOS 7
|
It conflicted because I had to re-ignore now that there is no inheritance in the yaml testing framework.
// Probably an enum, it's not clear exactly how we should handle this, but we currently only have one | ||
// thing which appears as OTHER | ||
o = getString(oneBasedColumn); |
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.
I think this is mostly in line as to what we have in other parts of the system (in DirectAccessAPI etc.) but we should formally decide as to how we want to treat our ENUMs. I think most of the DBs actually map it to either a STRING or INTEGER externally and do an implicit cast internally, but they loose some bits of type info in the way to do so.
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.
This was much needed since a long time! Thanks for tackling this.
Also, sorry for the delay
Conflicts on YamlIntegrationTests because the annotation was changed for the two enum tests on `main`, and the annotation was removed here.
This resolves #3073