Fix node retrieval fail with special characters in IDs for Postgres AGE GraphStorage #2320
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix node retrieval fail with special characters in IDs for Postgres AGE GraphStorage
Problem Statement
Nodes or edges with special characters (particularly double quotes) in their IDs were failing to be retrieved, causing the error.
Root Cause:
Node ID normalization was happening too early in single-node query methods (
get_node,node_degree,get_edge). When a node ID likeNode with "double quotes"was normalized before being passed to batch operations, it created key mismatches during result lookup, leading to:Solution
This PR refactors the normalization logic to ensure node IDs with special characters are correctly handled throughout the query pipeline:
Key Changes:
{original_id → original_id, normalized_id → original_id}Technical Implementation:
get_nodes_batch()andnode_degrees_batch()now handle normalization internallyExample Fix: