Timeline for Database design using Closure Table for tagging system
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 13 at 20:01 | history | bounty ended | CommunityBot | ||
| S Feb 13 at 20:01 | history | notice removed | CommunityBot | ||
| S Feb 5 at 18:28 | history | bounty started | xralf | ||
| S Feb 5 at 18:28 | history | notice added | xralf | Authoritative reference needed | |
| Feb 5 at 18:26 | history | edited | xralf | CC BY-SA 4.0 |
better example
|
| Jan 26 at 13:40 | answer | added | toolic | timeline score: 2 | |
| Jan 26 at 13:39 | history | edited | toolic | CC BY-SA 4.0 |
deleted 25 characters in body; edited title
|
| Jan 18 at 22:33 | comment | added | user272752 | Yes. This would not be parent/child, but made up of nodes and links. A node may be an "item" (eg: a book) or it may be a "category". I've not studied this SQL closely, but sense that starting from a clean slate would be better than "bending" existing code/paradigm trying to make it work as you desire. Cheers! | |
| Jan 18 at 21:51 | comment | added | xralf | So far I'm practicing this naiv solution - the tags are always unique and I try to specify more details in the tag, e.g. machine_learning_in_python etc. but I'm interested if there is a better solution, the tree structure will probably evolve to more general graph structure. | |
| Jan 18 at 21:48 | comment | added | xralf | @Fe2O3 Yes, I'm aware of this. | |
| Jan 18 at 19:49 | comment | added | user272752 | With multiple antecedents, have you considered that this would no longer be a "hierarchy"? Perhaps you want to shed that preconception... | |
| Jan 18 at 18:52 | history | edited | Reinderien |
edited tags
|
|
| Jan 17 at 22:02 | history | asked | xralf | CC BY-SA 4.0 |