type coercion
Open
correctness
enhancement
sql
- Dominant language
- Go
- Stars
- 24.4k
- Forks
- 873
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 108
Description
Our sql engine lacks (1) type safety and (2) type visibility. Both of these things are best done after plan building, during semantic resolution, before transformation rules. This would also help Doltgres, which probably doesn't want to reimplement type point fixes across the analyzer.
Partial PR implementation here: https://github.com/dolthub/go-mysql-server/pull/2150
problem overview here: https://docs.google.com/document/d/1AaoIGaoLktCFtQeqJLzJsQMKYL12K1GvnyVTq-WkeTg/edit
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.