TypeDB swaps implicit optionals for a real None type

Replacing implicit optionals with a None type in TypeDB

TypeDB swaps implicit optionals for a real None type

TypeDB has auto-unwrapped optional variables since version 3.4, a convenience that can quietly change a query's answers and leaves no way to test for emptiness. Version 3.15 deprecates that behavior and adds a native None type, an isset constraint for filtering unset variables, and if conditionals for write clauses. Making a variable optional now forces explicit handling downstream, much like Rust or Kotlin, so the compiler catches missing cases before queries run.

You don't just silently get a different answer set that looks okay, without considering the consequences.

More from this day

2026-11-21