Closed patroza closed 3 weeks ago
Should where("x", "neq", null)
filter out undefined
too?
Should
where("x", "neq", null)
filter outundefined
too?
no, undefined
and null
are not the same and undefined
is generally not a state we support in the storage model on the type level.
only for just in time migrations, but are then filled by the database via config.defaultValues (e.g defaultValues: { x: null }
will make a neq or eq for null hit, even when the field doesn't exist)
would be handled by #105
like https://github.com/effect-ts-app/libs/commit/4ab14def7441d084e8ff09db2db18b0473842cc0 but for
where("x", "neq", null)