Revision 4478
Added by Aaron Marcuse-Kubitza about 12 years ago
| schemas/vegbien.my.sql | ||
|---|---|---|
| 3730 | 3730 |
|
| 3731 | 3731 |
|
| 3732 | 3732 |
-- |
| 3733 |
-- Name: party_datasource; Type: INDEX; Schema: public; Owner: -; Tablespace: |
|
| 3734 |
-- |
|
| 3735 |
|
|
| 3736 |
|
|
| 3737 |
|
|
| 3738 |
|
|
| 3739 |
-- |
|
| 3740 | 3733 |
-- Name: party_unique; Type: INDEX; Schema: public; Owner: -; Tablespace: |
| 3741 | 3734 |
-- |
| 3742 | 3735 |
|
| schemas/vegbien.sql | ||
|---|---|---|
| 4289 | 4289 |
|
| 4290 | 4290 |
|
| 4291 | 4291 |
-- |
| 4292 |
-- Name: party_datasource; Type: INDEX; Schema: public; Owner: -; Tablespace: |
|
| 4293 |
-- |
|
| 4294 |
|
|
| 4295 |
CREATE UNIQUE INDEX party_datasource ON party USING btree (organizationname) WHERE (organizationname IS NOT NULL); |
|
| 4296 |
|
|
| 4297 |
|
|
| 4298 |
-- |
|
| 4299 | 4292 |
-- Name: party_unique; Type: INDEX; Schema: public; Owner: -; Tablespace: |
| 4300 | 4293 |
-- |
| 4301 | 4294 |
|
Also available in: Unified diff
schemas/vegbien.sql: party: Removed party_datasource unique index because it was causing problems with column-based import (due to multiple unique indexes covering the same columns in different ways), and because it prevented creation of more than one party per organization