-
-
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
feat(psql): introduce column type ltree
#604
Conversation
Thanks for this amazing library! I wanted to help introducing
Thanks in advance! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @EstebanBorai, sorry for the delay and thanks for contributing!!
I'd suggest adding a
Sure! Postgres specific operators goes to sea-query/src/extension/postgres/mod.rs Lines 13 to 28 in fd27b12
And its construct goes to sea-query/src/extension/postgres/expr.rs Lines 1 to 151 in fd27b12
That would be nice! But one step at a time, we should focus on bring it onto SeaQuery first. |
Just to be clear, the user will be responsible of running this code as part of writing migrations when using the |
You're right! |
Hey @EstebanBorai, would you like to introduce the follow things as discussed above?
|
Hi @billy1624! Here is a PR for the "Adding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is a Postgres only feature, we have to put it under extensions
. Please refer to the pg Type
statement.
@EstebanBorai hello! Any updates? |
Hi @ikrivosheev actually this PR is waiting for this other: #616 where Create Extension Statement is being introduced for PSQL! After that is merged I will be able to continue working on this! |
33436e4
to
3094255
Compare
Hi @billy1624 and @ikrivosheev ! Given that we landed #616 Im planning to move forward and introduce the |
ltree
ltree
af4ab9f
to
bc5e40e
Compare
bc5e40e
to
3569d54
Compare
Hi @billy1624 and @ikrivosheev! Im working on the
Is there a place where we could introduce them? I saw With regards to operators, it would be awesome to have access to them on ltreetest=> SELECT path FROM test WHERE path <@ 'Top.Science';
path
------------------------------------
Top.Science
Top.Science.Astronomy
Top.Science.Astronomy.Astrophysics
Top.Science.Astronomy.Cosmology
(4 rows) Then for functions I think its a bit more complex, we should be able to create queries like: ltreetest=> SELECT subpath(path,0,2)||'Space'||subpath(path,2) FROM test WHERE path <@ 'Top.Science.Astronomy';
?column?
------------------------------------------
Top.Science.Space.Astronomy
Top.Science.Space.Astronomy.Astrophysics
Top.Science.Space.Astronomy.Cosmology
(3 rows) Perhaps theres a way to partially introduce Thanks in advance! |
@ikrivosheev I just introduced the |
Hi guys! @billy1624 @ikrivosheev any updates on this? It would be awesome to merge this and move into SeoORM 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice and cleanly done. I'd probably add a doc test
🎉 Released In 0.30.3 🎉Thank you everyone for the contribution! |
PR Info
Introduces the
ltree
type for PostgreSQL.Aims to close: SeaQL/sea-orm#1476
New Features
ltree
support