-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQLite TEXT
data types specialization
#565
Comments
Should we? @tyt2y3 |
That is essentially what the other orms and query builders do. One thing that would be nice would be to document that so people dont have to read the source code to get the mapping (looking at you diesel 😅) |
@billy1624 this is a cool idea! But breaking changes. Well, on the other hand we have been talking about this for a long time and I saw similar issues. |
+1 on this proposal, and yes it would be nice if we can put a table in our rustdoc. |
I'd prefer adding a doctest to each methods in |
Hey @ikrivosheev, yes, please. Your help is greatly appreciated!! You can push commits directly to #566 :) |
FYI while I was building the diesel integration, I saw that |
Push. This is an issue we'd like to tackle once and for all. |
We also need this, looks like that generating entities w/sqlite isn't working so not usable (because information gets lost) |
Closed via #735 |
Motivation
Data types such as
DATE
,DATETIME
,UUID
... etc. All of them will be written asTEXT
data type when creating SQLite column.sea-query/src/backend/sqlite/table.rs
Lines 42 to 90 in bbd1c1e
This result in a "data lost": where
sea-schema
failed to discover the original data type of a column. E.g. ADATETIME
column will be treated asTEXT
.Proposed Solutions
Given that SQLite is essentially "typeless", we can simply write the specialized
TEXT
data types directly:The text was updated successfully, but these errors were encountered: