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

Remove error context handling from string literal hook #2736

Conversation

tanscorpio7
Copy link
Contributor

@tanscorpio7 tanscorpio7 commented Jul 11, 2024

Description

This change removes error context handling call from string literal hook. It seems to be better to have this call in engine so it happens on all code paths. Hook signature is simplified because passing parser state is no longer needed.

Engine PR: babelfish-for-postgresql/postgresql_modified_for_babelfish#408

Cherry Picked From: #2695

Issues Resolved

#2693

Sign Off

Author: Alex Kasko [email protected]
Signed-off-by: Tanzeel Khan [email protected]

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.

…-postgresql#2695)

This change removes error context handling call from string literal hook. It seems to be better to have this call in engine
so it happens on all code paths. Hook signature is simplified because passing parser state is no longer needed.

Engine PR: babelfish-for-postgresql/postgresql_modified_for_babelfish#397
Task: BABEL-5072
Signed-off-by: Alex Kasko <[email protected]>
Signed-off-by: Tanzeel Khan <[email protected]>
@tanscorpio7 tanscorpio7 deleted the BABEL_5072_2X branch July 26, 2024 18:34
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.

2 participants