You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sharding jdbc & proxy
version:3.1.0
when i use sql like
" select snapshot_no from pt_item_base_snapshot where snapshot_no ='20190304152137155168409726302111' "
sharding-sphere can't get the value of column snapshot_no correctly
, it's always be -1;
I debug the source code ,in the class PredicateExtractor ,the method buildExpression
only support number: Optional<ParserRuleContext> bitExprNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.BIT_EXPR); expressionNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.NUMBER); if (expressionNode.isPresent() && (!bitExprNode.isPresent() || 1 == bitExprNode.get().getChildCount())) { commonExpressionSegment.setValue(NumberUtil.getExactlyNumber(expressionNode.get().getText(), 10)); }
if I change code like ' expressionNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.STRING);' , the sql going well !
The text was updated successfully, but these errors were encountered:
sharding jdbc & proxy
version:3.1.0
when i use sql like
" select snapshot_no from pt_item_base_snapshot where snapshot_no ='20190304152137155168409726302111' "
sharding-sphere can't get the value of column snapshot_no correctly
, it's always be -1;
I debug the source code ,in the class PredicateExtractor ,the method buildExpression
only support number:
Optional<ParserRuleContext> bitExprNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.BIT_EXPR); expressionNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.NUMBER); if (expressionNode.isPresent() && (!bitExprNode.isPresent() || 1 == bitExprNode.get().getChildCount())) { commonExpressionSegment.setValue(NumberUtil.getExactlyNumber(expressionNode.get().getText(), 10)); }
if I change code like ' expressionNode = ExtractorUtils.findFirstChildNode(valueNode, RuleName.STRING);' , the sql going well !
The text was updated successfully, but these errors were encountered: