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

Add enum column support to relational server #3074

Merged
merged 3 commits into from
Feb 11, 2025

Conversation

ScottDugas
Copy link
Collaborator

@ScottDugas ScottDugas commented Jan 29, 2025

This resolves #3073

@foundationdb-ci
Copy link
Contributor

Result of fdb-record-layer-pr on Linux CentOS 7

  • Commit ID: 194e68e
  • Duration 0:57:51
  • Result: ✅ SUCCEEDED
  • Error: N/A
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@ScottDugas ScottDugas requested a review from g31pranjal February 3, 2025 12:05
@ScottDugas ScottDugas marked this pull request as ready for review February 3, 2025 15:21
It conflicted because I had to re-ignore now that there is no
inheritance in the yaml testing framework.
Comment on lines +324 to +326
// 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);
Copy link
Member

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.

g31pranjal
g31pranjal previously approved these changes Feb 11, 2025
Copy link
Member

@g31pranjal g31pranjal left a 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.
@ScottDugas ScottDugas merged commit 11e4826 into FoundationDB:main Feb 11, 2025
1 check passed
@ScottDugas ScottDugas added the enhancement New feature or request label Feb 14, 2025
@ScottDugas ScottDugas changed the title Resolves #3073: Add enum column support to relational server Add enum column support to relational server Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for enum columns to the relational server
3 participants