You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/05/11 21:54:49 UTC
[jira] [Commented] (CASSANDRA-4241) avoid hardcoding datatypes in
CQL grammar
[ https://issues.apache.org/jira/browse/CASSANDRA-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273555#comment-13273555 ]
Jonathan Ellis commented on CASSANDRA-4241:
-------------------------------------------
IMO this would make the code cleaner as well as get us a step closer to using custom types in CQL, should we want to allow that.
> avoid hardcoding datatypes in CQL grammar
> -----------------------------------------
>
> Key: CASSANDRA-4241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4241
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Jonathan Ellis
> Fix For: 1.2
>
>
> Currently adding a new datatype requires editing Cql.g as well as CFPropDefs. ISTM we can omit data type knowledge from the parser and just use \w+, and let our post-parser code reject invalid datatypes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira