-
Notifications
You must be signed in to change notification settings - Fork 30
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
Comments
@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. |
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 |
@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. |
@kilnerm Thanks for that great news. Any idea on when that will be ready ? |
@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. |
@kilnerm I'm not blaming you. I really love what you've done so far and 👏 for that. |
Would be great for JSONB type columns to use.
The text was updated successfully, but these errors were encountered: