Types: Improve type mappings#24
Conversation
9324bf1 to
120f8ea
Compare
daa7029 to
fea2527
Compare
4732e07 to
a63ce6e
Compare
c3efc82 to
e6837c0
Compare
e6837c0 to
1a0e14b
Compare
|
Dear @CaselIT, may we humbly ask you to give this patch a quick review? We started to overhaul the type mapping of the CrateDB dialect the other day, and would like to conclude this patch. Other than filling some gaps, we found that mapping database types to the uppercase type symbol variants provided by SQLAlchemy and back (i.e. using With kind regards, |
|
for reflected tables? it's fine, sqlalchemy types have |
|
Thank you! |
1a0e14b to
c722f01
Compare
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
bgunebakan
left a comment
There was a problem hiding this comment.
Thank you, There are 2 small things. Could you check?
5280304 to
b1a1b94
Compare
- Consequently use upper-case type definitions from `sqlalchemy.types`
- Add `timestamp without time zone` types (scalar and array)
- On SQLAlchemy 2, map `real` and `double{_precision}` types to the
newly introduced `sqltypes.{DOUBLE,DOUBLE_PRECISION}` types
All of this is intended to improve reverse type lookups / reflections.
b1a1b94 to
345f75d
Compare
About
sqlalchemy.typestimestamp without time zonetypes (scalar and array)realanddouble{_precision}types to thenewly introduced
sqltypes.{DOUBLE,DOUBLE_PRECISION}typesAll of this is intended to improve reverse type lookups / reflections.
References
ObjectArray.as_generic#23.