Timeline for Foreign key on PostgreSQL range bounds
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2017 at 12:07 | history | tweeted | twitter.com/StackDBAs/status/839085002818191360 | ||
| Mar 6, 2017 at 11:28 | vote | accept | Matjaž | ||
| Mar 6, 2017 at 11:03 | comment | added | Matjaž | I know, it was just an example. The idea behind it is to avoid overlapping ranges and the usage of the ranges instead of two columns is meant to compensate the multiple UNIQUE contraints and triggers to check the overlapping. | |
| Mar 6, 2017 at 10:51 | answer | added | ypercubeᵀᴹ | timeline score: 7 | |
| Mar 6, 2017 at 10:04 | comment | added | ypercubeᵀᴹ |
You know that these 2 designs are not equivalent. Did you mean to have UNIQUE constraints on both first_session and last_session?
|
|
| Mar 6, 2017 at 9:55 | history | asked | Matjaž | CC BY-SA 3.0 |