You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a good night's sleep on this decision, I found out that it is quite a complex one. After all, it not only involves a collection of Members, but it also has to be ordered.
Currently, we can link only one member to a subdecision, while for this type of subdecision, that therefore poses a problem. We should probably then leave this entirely to DBAL to write this collection away as an "array" (read comma-separated list). I do not think it is necessary to use an additional attribute to indicate the ordering of this list, because I cannot imagine any decisions where a different ordering would be useful.
What would you like?
A decision for the supporting of candidates for a new board.
Why is this needed?
While these decisions are only utilised once per association year (with some exceptions) I think it is a good idea to formalise it.
Other information
No response
The text was updated successfully, but these errors were encountered: