Timeline for Unique constraint to enforce max one null per item
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2014 at 18:42 | history | edited | Erwin Brandstetter | edited tags | |
| Aug 27, 2014 at 18:41 | comment | added | Erwin Brandstetter | I reopened the question, since you have sneaked in a second question (we prefer one question per question). This may be of help for the main question (unique and NULL): Multi-column unique constraint and NULL values. And this for the 2nd one (exclusion constraint): Preventing adjacent/overlapping entries with EXCLUDE in PostgreSQL | |
| Aug 27, 2014 at 18:30 | history | reopened | Erwin Brandstetter postgresql Users with the postgresql badge or a synonym can single-handedly close postgresql questions as duplicates and reopen them as needed. | ||
| Aug 27, 2014 at 18:29 | history | closed | Erwin Brandstetter postgresql Users with the postgresql badge or a synonym can single-handedly close postgresql questions as duplicates and reopen them as needed. | Duplicate of PostgreSQL multi-column unique constraint and NULL values | |
| Aug 27, 2014 at 7:25 | vote | accept | vektor | ||
| Aug 27, 2014 at 6:59 | answer | added | user1822 | timeline score: 11 | |
| Aug 27, 2014 at 6:12 | history | asked | vektor | CC BY-SA 3.0 |