[ 
https://issues.apache.org/jira/browse/GEODE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235397#comment-16235397
 ] 

ASF GitHub Bot commented on GEODE-3938:
---------------------------------------

jujoramos commented on issue #1003: Fix for GEODE-3938
URL: https://github.com/apache/geode/pull/1003#issuecomment-341352262
 
 
   Hey @jhuynh1 ,
   Thanks for reviewing this PR, I've updated it with your changes.
   Cheers.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Allow query parameters within the to_date preset query function
> ---------------------------------------------------------------
>
>                 Key: GEODE-3938
>                 URL: https://issues.apache.org/jira/browse/GEODE-3938
>             Project: Geode
>          Issue Type: New Feature
>          Components: querying
>            Reporter: Juan José Ramos Cassella
>            Assignee: Juan José Ramos Cassella
>
> Currently the {{to_date}} preset query function doesn't allow the user to 
> pass the date to format as a query parameter, which forces the user 
> application to add boilerplate code to manually parse the date.
> Apparently there's no internal blockers preventing such a feature to be 
> enabled, and the change just implies a small change in {{oql.g}}:
> {code}
> conversionExpr :
>   (
>     ...
>         |
>            (  
>               (
>                
> "to_date"^<AST=org.apache.geode.cache.query.internal.parse.ASTConversionExpr>
>               )
>               TOK_LPAREN!
>               (stringLiteral | queryParam) TOK_COMMA! stringLiteral
>               TOK_RPAREN! 
>            )    
>     ...
>   )
>     ;
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to