Add missing mention of 4927 in CQL3 changelog

Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/97170024
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/97170024
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/97170024

Branch: refs/heads/trunk
Commit: 9717002498e361f889b7498c419b22513095f73a
Parents: 07ebbe5
Author: Sylvain Lebresne <[email protected]>
Authored: Fri Jan 18 14:38:50 2013 +0100
Committer: Sylvain Lebresne <[email protected]>
Committed: Fri Jan 18 14:38:50 2013 +0100

----------------------------------------------------------------------
 doc/cql3/CQL.textile |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cassandra/blob/97170024/doc/cql3/CQL.textile
----------------------------------------------------------------------
diff --git a/doc/cql3/CQL.textile b/doc/cql3/CQL.textile
index ac674e3..a4d803c 100644
--- a/doc/cql3/CQL.textile
+++ b/doc/cql3/CQL.textile
@@ -964,6 +964,7 @@ The following describes the addition/changes brought for 
each version of CQL.
 h3. 3.0.1
 
 - "Date strings":#usingdates (and timestamps) are no longer accepted as valid 
@timeuuid@ values. Doing so was a bug in the sense that date string are not 
valid @timeuuid@, and it was thus resulting in "confusing 
behaviors":https://issues.apache.org/jira/browse/CASSANDRA-4936.  However, the 
following new methods have been added to help working with @timeuuid@: @now@, 
@minTimeuuid@, @maxTimeuuid@ , @dateOf@ and @unixTimestampOf@. See the "section 
dedicated to these methods":#usingtimeuuid for more detail.
+- "Float constants"#constants now support the exponent notation. In other 
words, @4.2E10@ is now a valid floating point value.
 
 
 h2. Versioning

Reply via email to