The NOT NULL Constraint in BigQuery

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
Search for a command to run...

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
No comments yet. Be the first to comment.
Short, practical posts on SQL and BigQuery — from core language features to advanced query patterns. A reference for data practitioners at every level.
If you're looking to generate a random number in BigQuery, check out the RAND() function. It's a pseudo-random number generator, generating a float in the interval [0, 1). I've used it a few times before, but for the today's exercise, I've decide to ...
Here's a useful Dataform concept: pre_operations and post_operations. As the name implies, these represent a set of actions that run before and after the main operation (table, view, or SQL operations

BigQuery has always been a SQL engine for tabular data. Object tables add an interesting twist to that. Instead of rows containing values, an object table gives you one row per file — pointing at da

Query your data lake with warehouse-grade security and performance — without moving a single file.

Ever run a heavy BigQuery SQL query, processed gigabytes of data — and then accidentally closed the tab or forgot to save the results? 😬 Don't re-run it. Your results are still there. BigQuery automa

You can use query parameters in BigQuery hashtag#SQL (now in the console as well!) — but how are they different from variables, and when should you use each? Both parameters and variables act as place

Are you using the NOT NULL constraint in BigQuery? This constraint is a staple when working with databases.
So, when creating a table, you have the option to declare if a particular column is required and should not be null. We do that by simply adding the NOT NULL to the column declaration.
You also can check it on an existing table by checking the column (field) MODE.
It can have 3 values:
- NULLABLE (which is the default if you've haven't set anything)
- REQUIRED (if you've set NOT NULL for this columns)
- REPEATED (for ARRAYS).
Upon trying insert or update data that will violated this constraint, the statement will fail.
Overall, setting the right MODE for your field helps enforce your expectations about the data that should be inserted or updated in a particular table.

Found it useful? Subscribe to my Analytics newsletter at notjustsql.com.