Timeline for Enforcing constraints across databases
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2017 at 15:27 | vote | accept | CommunityBot | ||
| Oct 27, 2017 at 18:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 27, 2017 at 17:14 | answer | added | Batavia | timeline score: 1 | |
| Sep 27, 2017 at 16:54 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 28, 2017 at 20:22 | comment | added | Kwebble | All departments (verticals) basically use the same business entity, the project in your example. Is it not required to have a company wide shared entity to prevent each department form inventing their own information structure and incompatible business rules? | |
| Aug 28, 2017 at 16:36 | comment | added | Pieter B | Your first requirement change will be to make names mutable. | |
| Aug 28, 2017 at 16:23 | answer | added | Hugh Morris | timeline score: 0 | |
| Aug 17, 2017 at 17:01 | comment | added | user209881 | @RobertHarvey thanks! I think this will help with the data model issue quite a bit. | |
| Aug 17, 2017 at 16:24 | comment | added | Robert Harvey | Using Globally-Unique Identifiers (GUID's) as primary keys would be a good start. | |
| Aug 17, 2017 at 16:09 | history | edited | Robert Harvey | CC BY-SA 3.0 |
deleted 62 characters in body
|
| Aug 17, 2017 at 15:44 | history | asked | user209881 | CC BY-SA 3.0 |