Revision 13586
Added by Aaron Marcuse-Kubitza over 10 years ago
| trunk/inputs/.TNRS/schema.sql | ||
|---|---|---|
| 736 | 736 |
-- Name: tnrs__valid_match; Type: INDEX; Schema: TNRS; Owner: -; Tablespace: |
| 737 | 737 |
-- |
| 738 | 738 |
|
| 739 |
CREATE UNIQUE INDEX tnrs__valid_match ON tnrs USING btree ("Name_submitted") WHERE is_valid_match;
|
|
| 739 |
CREATE INDEX tnrs__valid_match ON tnrs USING btree ("Name_submitted") WHERE is_valid_match;
|
|
| 740 | 740 |
|
| 741 | 741 |
|
| 742 | 742 |
-- |
| trunk/schemas/vegbien.sql | ||
|---|---|---|
| 17639 | 17639 |
-- Name: tnrs__valid_match; Type: INDEX; Schema: TNRS; Owner: -; Tablespace: |
| 17640 | 17640 |
-- |
| 17641 | 17641 |
|
| 17642 |
CREATE UNIQUE INDEX tnrs__valid_match ON tnrs USING btree ("Name_submitted") WHERE is_valid_match;
|
|
| 17642 |
CREATE INDEX tnrs__valid_match ON tnrs USING btree ("Name_submitted") WHERE is_valid_match;
|
|
| 17643 | 17643 |
|
| 17644 | 17644 |
|
| 17645 | 17645 |
SET search_path = geoscrub, pg_catalog; |
Also available in: Unified diff
fix: inputs/.TNRS/schema.sql: tnrs.tnrs__valid_match index: made it non-unique to allow multiple matches per name, as is needed to implement #917