Structures look interesting because you can reorder entries manually, generate breadcrumbs and visually see a hierarchy of entries. Besides this, what are the primary consideration when choosing a Structure over a Channel?
Add a comment
|
1 Answer
Ordering and Hierarchy are the main benefits but they create a couple of side benefits such as the ability to
- get the "children" and "parents" of an entry
- get siblings including next and previous siblings
The best part is there no real downside, they have all the features and functions of a regular channel PLUS the structure.
-
1Also worth noting: You can always convert a Channel into a Structure or vice versa, without loosing field-data.– VictorSep 7, 2014 at 18:37
-
3The only downside of a structure over a channel is that there is overhead associated with keeping track of all that extra information (hierarchy, ordering, etc.). If you don't need the features of a structure, then a channel is much more efficient.– Brad Bell ♦Sep 7, 2014 at 19:47
-
2"much more efficient" - how much so? What sort of performance impact are we talking here? Apr 25, 2016 at 10:27
-
I see no one replied to that for years, but I'll chime in: it's more efficient on large websites to use channels instead of structure because mysql has to make extra queries and fetch extra data to generate pagination (prev entry, next entry, count entries to generate number of pages, etc.). You can see a similar performance problem with WordPress (if you don't use pagination, you can declare an option called "no_found_rows" that removes those extra queries). On a smaller database, it's not much noticeable though, so take with a grain of salt. Oct 28, 2022 at 14:33