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
SQLite’s flexibility with column datatypes is nice, but it can sometimes be confusing when the actual datatype doesn’t match the column type. For example, a column might be set to INTEGER, but the stored data is a REAL. It would be awesome if there was a little visual indicator, like a small marker in the top right corner of the cell, to show when this happens.
When you hover over the marker, it could show a tooltip saying something like, "Expected type: INTEGER, received: REAL." This would give users a quick heads-up when there’s a type mismatch, making it easier to spot and deal with.
This can happen on several occasions. In practice, SQLite only officially supports 4 data types (plus NULL, which is not a "pure type"): INTEGER (123), REAL (1.23), TEXT ("abc") and BLOB (X'616263', binary for "abc").
Thanks for considering this!
The text was updated successfully, but these errors were encountered:
(Following #137)
SQLite’s flexibility with column datatypes is nice, but it can sometimes be confusing when the actual datatype doesn’t match the column type. For example, a column might be set to INTEGER, but the stored data is a REAL. It would be awesome if there was a little visual indicator, like a small marker in the top right corner of the cell, to show when this happens.
When you hover over the marker, it could show a tooltip saying something like, "Expected type: INTEGER, received: REAL." This would give users a quick heads-up when there’s a type mismatch, making it easier to spot and deal with.
This can happen on several occasions. In practice, SQLite only officially supports 4 data types (plus
NULL
, which is not a "pure type"):INTEGER
(123),REAL
(1.23),TEXT
("abc") andBLOB
(X'616263', binary for "abc").Thanks for considering this!
The text was updated successfully, but these errors were encountered: