Skip to content
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

Question: Any plans for the nested structures #17

Open
fobin opened this issue Mar 9, 2018 · 6 comments
Open

Question: Any plans for the nested structures #17

fobin opened this issue Mar 9, 2018 · 6 comments
Labels
question Further information is requested

Comments

@fobin
Copy link

fobin commented Mar 9, 2018

Would be great for JSONB type columns to use.

@kilnerm kilnerm added the question Further information is requested label Nov 19, 2018
@kilnerm
Copy link
Contributor

kilnerm commented Nov 19, 2018

@fobin, We do have plans to add support for nested Structures along with dictionaries and arrays.

JSONB column support is probably a different piece of work as it will take a little more than simply encoding/decoding a struct. We will have to enhance the underlying plugins to add support for the base column type as a starting point.

@dillan
Copy link

dillan commented Jun 1, 2019

Relationships definitely seem like very important functionality for an ORM. @kilnerm Do you know if there is existing headway being made on relationship support?

I see a branch from @EnriqueL8 that looks like it's heading in that direction but hasn't been active in a while.

https://github.com/IBM-Swift/Swift-Kuery-ORM/compare/support_dictionary

@kilnerm
Copy link
Contributor

kilnerm commented Jun 3, 2019

@dillan I have been spending some time coming up with a design for how we can implement relationships. I will be opening some issues in the near future that detail how this will all piece together. I'm keen to get started on implementation as soon as possible.

@jfgrang
Copy link

jfgrang commented Aug 6, 2019

@kilnerm Thanks for that great news. Any idea on when that will be ready ?
In the meantime I am really interested in knowing a workaround for that.

@kilnerm
Copy link
Contributor

kilnerm commented Aug 12, 2019

@jfgrang I'm afraid the timeline is fluid, I spend as much time as I can spare on this and have made some reasonable progress regarding the nesting of models.

Working around this is not trivial, firstly you would need to declare your tables to include appropriate foreign key relationships and then add functions, that handle the nesting, to your structs for the database operations you require.

@jfgrang
Copy link

jfgrang commented Aug 12, 2019

@kilnerm I'm not blaming you. I really love what you've done so far and 👏 for that.
I was considering doing the nested part that way. Thanks for your guidance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants