@effect/sql. It's not been the easiest to grasp but I'm learning to love it!! @effect/sql because one writes the schemas of the rows rather than tables and the migrations are written by hand, I feel like type safety is lost here. For example, a column that is declared as nullable in the db could by mistake be declared in effect's Schema as non-nullable. Since one of the strengths of @effect is improving type safety, this just feels a bit of a downgrade compared to the other packages. Are there any other workarounds around this that people may have found?