You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently ColumnLike has two generic types: 1.) the type from the database, 2.) the type it should be used as in Scala.
I think we should only have the type in the database and leave it up to mapper, queries, etc. to do on-demand conversion as different queries need data in different ways (Option[Int], Int, Ref, String, Long, etc.)
This should both simplify setting up the tables in the first place as well as increase the flexibility of the system overall.
The text was updated successfully, but these errors were encountered:
Currently ColumnLike has two generic types: 1.) the type from the database, 2.) the type it should be used as in Scala.
I think we should only have the type in the database and leave it up to mapper, queries, etc. to do on-demand conversion as different queries need data in different ways (Option[Int], Int, Ref, String, Long, etc.)
This should both simplify setting up the tables in the first place as well as increase the flexibility of the system overall.
The text was updated successfully, but these errors were encountered: