Revision 1319
Added by Aaron Marcuse-Kubitza about 12 years ago
| vegbien.my.sql | ||
|---|---|---|
| 3191 | 3191 |
|
| 3192 | 3192 |
|
| 3193 | 3193 |
-- |
| 3194 |
-- Name: namedplace_unique; Type: CONSTRAINT; Schema: public; Owner: -; Tablespace: |
|
| 3195 |
-- |
|
| 3196 |
|
|
| 3197 |
ALTER TABLE namedplace |
|
| 3198 |
ADD CONSTRAINT namedplace_unique UNIQUE (rank, placename); |
|
| 3199 |
|
|
| 3200 |
|
|
| 3201 |
-- |
|
| 3194 | 3202 |
-- Name: namedplacecorrelation_pkey; Type: CONSTRAINT; Schema: public; Owner: -; Tablespace: |
| 3195 | 3203 |
-- |
| 3196 | 3204 |
|
| ... | ... | |
| 4184 | 4192 |
|
| 4185 | 4193 |
|
| 4186 | 4194 |
-- |
| 4187 |
-- Name: namedplace_unique; Type: INDEX; Schema: public; Owner: -; Tablespace: |
|
| 4188 |
-- |
|
| 4189 |
|
|
| 4190 |
|
|
| 4191 |
|
|
| 4192 |
|
|
| 4193 |
-- |
|
| 4194 | 4195 |
-- Name: note_accessioncode_index; Type: INDEX; Schema: public; Owner: -; Tablespace: |
| 4195 | 4196 |
-- |
| 4196 | 4197 |
|
Also available in: Unified diff
vegbien.sql: namedplace: Removed parent_id from unique constraint because some data might be missing intervening links (e.g. state for a county, country), but the place (e.g. county) should still be attached to the existing place of the same name and rank (which will hopefully already have the correct parent_id link)