Timeline for Allowing null to a foreign key
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2016 at 20:30 | comment | added | JeffO | +1 for keeping as much of the current schema as possible. | |
| Aug 22, 2016 at 13:24 | comment | added | Tulains Córdova | @Tikkes I changed the model so FROM_DATE is part of the PK to allow same plant/model combinations but on a different timeframe. You have to implement a sanity check trigger of method to avoid date overlaps. Time overlaps cannot be avoided by design alone. | |
| Aug 22, 2016 at 13:23 | history | edited | Tulains Córdova | CC BY-SA 3.0 | added 2 characters in body |
| Aug 22, 2016 at 13:20 | vote | accept | Tikkes | ||
| Aug 22, 2016 at 13:11 | comment | added | Tikkes | This is a great answer yet I have one more question concerning the time constraint. If, at any time, I want to re-enable a plant/model combination but on a different timeframe. How would you go about that considering that I would like to keep a history for example? | |
| Aug 22, 2016 at 12:13 | history | edited | Tulains Córdova | CC BY-SA 3.0 | added 136 characters in body |
| Aug 22, 2016 at 12:04 | history | answered | Tulains Córdova | CC BY-SA 3.0 |