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

Make NEWID() and NEWSEQUENTIALID() functions VOLATILE #2540

Conversation

lejaokri
Copy link
Contributor

@lejaokri lejaokri commented May 2, 2024

Brief History

From GA to 14.6/15.1
NEWID() is VOLATILE [this is correct]

From 14.7/15.2 to 14.11/15.6
NEWID() is STABLE [this is wrong]

From 14.12/15.7
NEWID() should be VOLATILE

Description

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@coveralls
Copy link
Collaborator

coveralls commented May 2, 2024

Pull Request Test Coverage Report for Build 8932779828

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 73.045%

Totals Coverage Status
Change from base Build 8925979479: 0.0%
Covered Lines: 41453
Relevant Lines: 56750

💛 - Coveralls

@lejaokri lejaokri force-pushed the klejao-babel-4923-3x branch 4 times, most recently from 415564a to 8ee4087 Compare May 2, 2024 19:15
2jungkook
2jungkook previously approved these changes May 2, 2024
@2jungkook 2jungkook self-requested a review May 2, 2024 21:21
@lejaokri lejaokri force-pushed the klejao-babel-4923-3x branch 2 times, most recently from 4a7f516 to 322fb0d Compare May 2, 2024 22:02
Altering a table to add a column with DEFAULT NEWID() makes
the values all the same value which is not the correct bheaviour.
This is because NEWID and NEWSEQUENTIALID are both STABLE when
then should be VOLATILE.

Task: BABEL-4923
Signed-off-by: Kristian Lejao <klejao@amazon.com>
@Deepesh125 Deepesh125 merged commit db9e465 into babelfish-for-postgresql:BABEL_3_X_DEV May 3, 2024
40 checks passed
@Deepesh125 Deepesh125 deleted the klejao-babel-4923-3x branch May 3, 2024 06:38
staticlibs pushed a commit to wiltondb/babelfish_extensions that referenced this pull request May 4, 2024
…postgresql#2540)

Altering a table to add a column with DEFAULT NEWID() makes the values all the same value which is not the correct
behaviour. This is because NEWID and NEWSEQUENTIALID are both STABLE when it should be VOLATILE.

Task: BABEL-4923
Signed-off-by: Kristian Lejao <klejao@amazon.com>
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

Successfully merging this pull request may close these issues.

None yet

5 participants