if it's not set it will be the BytesTypes where validation is a no-op.
IMHO best to keep that validation in your app.
Aaron
On 19 Apr 2011, at 01:30, Sasha Dolgy wrote:
> So, in the instance of a simple CF for user data:
>
> username
> fullname
> birthdate
>
> If birthdate is unix timestamp
So, in the instance of a simple CF for user data:
username
fullname
birthdate
If birthdate is unix timestamp, it wont need the UTF8 validator. The
other 2 columns could. Does this then mean that a default should
-not- be set for the column family?
-sd
On Mon, Apr 18, 2011 at 3:27 PM, Jonathan
No.
But, it is not recommended to mix default_validation_class and column
definitions. If you have a relatively static set of columns, column
definitions are recommended.
On Mon, Apr 18, 2011 at 2:23 AM, Sasha Dolgy wrote:
> Hi all,
>
> When defining a new column family, there is the possiblity
