#3037 closed Enhancement (wontfix)
Consider adding parent_guid to objects_entity table
| Reported by: | ewinslow | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Near Term Future Release |
| Component: | Core | Version: | 1.7 |
| Severity: | minor | Keywords: | |
| Cc: | brett@…, juho.jaakkola@… | Difficulty: |
Description (last modified by ewinslow)
It's used in pages, it could be used with ElggComment. We have a similar need in our forum code. I know people have wanted to have nested categories, which this would support nicely. It could be useful for nesting menu items as well.
Worth adding to the objects table? (I don't see the use in any other context). Or should we just stay strong with encouraging the use of relationships for this?
Change History (3)
comment:1 Changed 11 months ago by juho.jaakkola
- Cc juho.jaakkola@… added
comment:2 Changed 11 months ago by ewinslow
- Description modified (diff)
- Resolution set to wontfix
- Status changed from new to closed
comment:3 Changed 11 months ago by cash
Agree with Evan.
Also, the pages shouldn't use metadata to store relationship to parent relationship. We should fix that.
Note: See
TracTickets for help on using
tickets.
I'd prefer use of relationships for this. The ElggComment and ElggPage semantics are different -- one is really a "reply-to" relationship, whereas the other is a parent-child relationship. It would be weird to conflate these two.
Closing unless someone else feels differently.