On Sun, Apr 13, 2025 at 9:24 AM Patrick McFadin <pmcfa...@gmail.com> wrote:
> I'm loving all the syntax discussion lately. It's a good debate and > essential for the project's future with a good developer experience. > +1 > On NULL. I've been asked this a million times by end users. Why is there > no "NOT NULL" in the schema? > I would've expected this to be in billions by now ;) > I'm in favor of the standard SQL syntax here because it's what users have > been using forever: > name text NOT NULL > I hold a weak opinion on this. We don't have to necessarily align on to the standard SQL syntax. In my experience, users subconsciously feel Cassandra is a SQL database and try to design their schema to fit the traditional SQL / RDBMS design and then later are disappointed to find out it doesn't have joins or foreign key constraints. But that's just my personal experience working with users. However, I think we should strive for consistency and if it aligns with SQL I have no issues with the syntax. Just sharing my experience. > On CHECK. Also in favor of making this a reserved word but in context. > Namely, how Postgres SQL works. CHECK ( boolean_expression_on_column) > Making CHECK a reserved keyword may result in issues that Scott described. It will present a substantial barrier for users to upgrade as applications will have to be updated. Thanks, Dinesh
