Timeline for Force Arcmap to respect primary key constraints/triggers
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2016 at 18:29 | vote | accept | Mojimi | ||
| Dec 23, 2016 at 17:03 | answer | added | Albert Godfrind | timeline score: 2 | |
| Dec 23, 2016 at 16:43 | comment | added | Albert Godfrind | "I've never used a primary key constraint in 28 years as an Oracle DBA. They're slow and needlessly complicate implementation." Wow. That's a strong statement. And a false one too. Where did you find out that PKs are slow ? And why do they complicate implementation ? Having proper referential integrity in a data model is essential to maintain - well, integrity. Prevent pesky things like orphan child records and duplicate keys ... | |
| Dec 23, 2016 at 16:39 | comment | added | Albert Godfrind | "Not only that but it overwrites the BEFORE INSERT trigger by putting 0 after it triggered." Sorry, that is just not possible. The before insert triggers executes when you issue the INSERT statement. There is no place where anyone could change that value before the INSERT completes. The only place that can happen is within the BEFORE INSERT trigger itself. Maybe the logic in your trigger is to only fill the primary key column with a number when the value it receives is not null ? Just change that code to also set a new number if the value is 0. | |
| Dec 23, 2016 at 4:29 | answer | added | Devdatta Tengshe | timeline score: 3 | |
| Dec 22, 2016 at 1:14 | history | tweeted | twitter.com/StackGIS/status/811741681808773120 | ||
| Dec 21, 2016 at 23:27 | comment | added | Vince | There's two models at work, and they conflict. I've never used a primary key constraint in 28 years as an Oracle DBA. They're slow and needlessly complicate implementation. If you're inserting rows exclusively with ArcGIS, use ArcGIS-compatible techniques to populate rows. | |
| Dec 21, 2016 at 23:15 | comment | added | Mojimi | @Vince can a pk even be not null? | |
| Dec 21, 2016 at 23:14 | comment | added | Vince | The issue is the NOT NULL. If you don't declare it NOT NULL, then your database-provided value will populate. | |
| Dec 21, 2016 at 22:24 | history | edited | Mojimi |
edited tags
|
|
| Dec 21, 2016 at 20:20 | history | edited | Mojimi | CC BY-SA 3.0 |
deleted 9 characters in body
|
| Dec 21, 2016 at 17:53 | history | asked | Mojimi | CC BY-SA 3.0 |