Details
-
Sub-task
-
Status: Resolved
-
Low
-
Resolution: Fixed
Description
String
Anything between double-quotes. Node-side this is just converted to bytes, so it could really be used to represent any type so long as it is appropriately encoded.
Examples:
SELECT "name" FROM cf; UPDATE cf SET "name" = "value" WHERE KEY = "key";
UTF-8
A double-quoted string literal that is prefixed with a "u" to indicated that it should be encoded to bytes using the utf-8 charset node-side.
Examples:
SELECT u"name" FROM cf; UPDATE cf SET u"name" = u"value" WHERE KEY = "key";
Integer
An undecorated numeric literal, converted to a 4-byte int node-side.
Examples:
SELECT 10..100 FROM cf WHERE KEY = "key"; UPDATE cf SET 1000 = "thousand", 100 = "hundred" WHERE KEY = "key";
Long
A numeric literal suffixed with an "L", converted to an 8-byte long node-side.
Examples:
SELECT 10L..100L FROM cf WHERE KEY = "key"; UPDATE cf SET 1000L = "thousand", 100L = "hundred" WHERE KEY = "key";
UUID
A string-formatted UUID supplied as an "argument" to a ctor/function formated string (uuid(<uuid string>)). Node-side this is converted back to the corresponding UUID.
Examples:
SELECT uuid(5f989e95-ae07-4425-b84a-6876ba106c66) FROM cf WHERE KEY = "key"; UPDATE cf SET uuid(5621b93d-d3a2-4d22-8a59-bdb93202b6cb) = "username" WHERE KEY = "key";
TimeUUID (UUID Type 1)
A string-formatted time-based UUID (type 1) supplied as an "argument" to a ctor/function formated string (timeuuid(<uuid string>)). Node-side this is converted back to the corresponding UUID. In addition to a string-formatted UUID, it should also be possible to supply dates in a variety of formats which will result in a new UUID being created node-side.
Examples:
SELECT timeuuid(2011-01-01)..timeuuid(2010-01-21) FROM cf WHERE KEY = "key"; UPDATE cf SET timeuuid(now) = 1000L WHERE KEY = "key";