Timeline for How can I change a field cardinality?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2019 at 12:10 | history | edited | Berdir | CC BY-SA 4.0 |
added 4 characters in body
|
| Feb 15, 2019 at 15:06 | comment | added | Kelley Curry | This is great information. I always took that message literally and never tried to change it. One clarification: I initially interpreted Berdir's answer as meaning you could raise the cardinality but not lower it, but in fact he means you can't set it lower than the highest number of values you currently have in the database. So by finding the two pieces of content I had that were above my desired limit and deleting their extra items, I was then able to change the field cardinality from Unlimited to 1 through the UI — no migration or update hooks required. | |
| Sep 11, 2018 at 8:36 | comment | added | Berdir | For the same site more likely an update hook, in-site-migration isn't really a thing yet. But the only thing that update hook could do is delete the additional values that are above the new limit that you want to set if it's too much to do it manually. | |
| Sep 10, 2018 at 18:04 | vote | accept | Jed Anderson | ||
| Sep 10, 2018 at 18:04 | comment | added | Jed Anderson | Thanks Berdir! That answers my short term question. For the future, if I did need to reduce cardinality, would I write a migration or an update hook? | |
| Sep 9, 2018 at 15:28 | history | answered | Berdir | CC BY-SA 4.0 |