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
We have been going over a lot of naming conventions for our database. I would like to start recording the ideas and why they work/don't.
Using timestamps for stateful boolean column
This applies to having an archived state of an item. We attempted to draw a line at when a column is an action (e.g. archive) rather than a property (e.g. is_red). This idea means that we convert these "action" states to timestamp fields over booleans (e.g. archived_at: timestamp).
Conclusion
In order to keep data consistent, we must introduce the timestamp from a single service. This means that we must introduce an alternative endpoint to performing this action (e.g. PUT /item/:id/archive). This is fine but can lead to complications with pedantic REST frameworks.
Spring MVC Validation - FAQ: Is it possible to integrate multiple validation string in one annotation?
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters