> When creating a table in all ANSI-SQL compliant RDBMS' the VARCHAR datatype > takes a numeric parameter, however this parameter is generating errors in > CQL3. >
CQL3 is *not* ANSI-SQL compliant and will never be. It's not even SQL. > I would like to propose that the column length be allowed in the grammar > (but ignored by cassandra), allowing better ANSI-SQL client compatibility. > I agree with Ed and disagree with your proposal. Allowing a length constraint but not respecting it would only help people to shoot themselves in the foot, as they would be led to believe Cassandra does validate the length where it doesn't. If would be acceptable to add the length only if we do respect it. Which is something we could do, though adding it "just" to make it close to ANSI-SQL honestly doesn't interest me much (adding it because it's useful would be a better argument however) because again, CQL is not SQL. In particular, you don't model application with CQL the same way you do with SQL, and so using a SQL application in CQL without modification is not a good idea. Besides, I doubt any non-trivial SQL application could be used as is in CQL, due to the lack of join for instance. -- Sylvain
