Timeline for Force Arcmap to respect primary key constraints/triggers
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2016 at 0:12 | comment | added | Albert Godfrind | The OBJECTID may still be used by ArcGIS to fetch individual rows. That just means it must contain unique values. That can be enforced with a unique index (or a unique constraint). | |
| Dec 24, 2016 at 23:55 | comment | added | User1974 | What will happen when that table with the ID as the primary key is registered with the geodatabase? An OBJECTID field will be created right? Isn't the OBJECTID supposed to be the primary key? gis.stackexchange.com/q/222527/62572 | |
| Dec 23, 2016 at 18:29 | vote | accept | Mojimi | ||
| Dec 23, 2016 at 18:29 | comment | added | Mojimi | You are correct, I did some tests and now it works? Not sure if something changed, maybe my trigger was wrong somehow, anyway thanks! | |
| Dec 23, 2016 at 17:09 | history | edited | Albert Godfrind | CC BY-SA 3.0 |
format numbered list
|
| Dec 23, 2016 at 17:03 | history | answered | Albert Godfrind | CC BY-SA 3.0 |