I think we're closing in on something workable.
Dropping TRANSPOSED from Gamma as redundant with respect to the
composite PRIMARY KEY definition.
Should we support column values in non-sparse rows by adding a
VALUE(column_name) section?
CREATE TABLE timeline (
user_id int,
posted_at uuid
+1 on Gamma
+1 on haveing capability to specify a value.
My only reservation is the choice of the keword "TABLE", which is going to
be a source of continued confusion.
On Fri, Dec 30, 2011 at 11:58 AM, Jonathan Ellis wrote:
> I think we're closing in on something workable.
>
> Dropping TRANSPO
On Fri, Dec 30, 2011 at 10:58 AM, Jonathan Ellis wrote:
> I think we're closing in on something workable.
I agree.
> Dropping TRANSPOSED from Gamma as redundant with respect to the
> composite PRIMARY KEY definition.
+1
> Should we support column values in non-sparse rows by adding a
> VALUE(c
On Fri, Dec 30, 2011 at 11:12 AM, Rick Shaw wrote:
> +1 on Gamma
> +1 on haveing capability to specify a value.
>
> My only reservation is the choice of the keword "TABLE", which is going to
> be a source of continued confusion.
TABLE is an alias for COLUMNFAMILY (pretty much always has been); I
