Pass CHARACTER VARYING(50) DEFAULT ''::CHARACTER VARYING NOT NULL,Ĭreated_date TIMESTAMP(6) WITHOUT TIME ZONE DEFAULT "statement_timestamp"(), Login CHARACTER VARYING(30) DEFAULT ''::CHARACTER VARYING NOT NULL, Hourlyrate NUMERIC(6,2) DEFAULT 0 NOT NULL, Mobile CHARACTER VARYING(40) DEFAULT NULL::CHARACTER VARYING,įax CHARACTER VARYING(40) DEFAULT NULL::CHARACTER VARYING, Phone CHARACTER VARYING(50) DEFAULT NULL::CHARACTER VARYING, Position CHARACTER VARYING(80) DEFAULT ''::CHARACTER VARYING,Įmail CHARACTER VARYING(50) DEFAULT NULL::CHARACTER VARYING, Name_last CHARACTER VARYING(80) DEFAULT ''::CHARACTER VARYING,Ĭompany CHARACTER VARYING(255) DEFAULT ''::CHARACTER VARYING,īusinesstype CHARACTER VARYING(80) DEFAULT ''::CHARACTER VARYING, Name_first CHARACTER VARYING(80) DEFAULT ''::CHARACTER VARYING, Id BIGINT DEFAULT "nextval"('"ja_customers_id_seq"'::"regclass") NOT NULL, Reply to this email directly or view it on GitHub So when I do the import - I don't get the data from that tables. file=public_dm_integrations_.sql -limit="public.* = 1000" -verbose pg_sample dbname -exclude-table-data='junk. I bet it was the fact that we removed the DISTINCT. Psql:all_data_second.sql:28828033: ERROR: duplicate key value violates unique constraint "spatial_ref_sys_pkey"ĭETAIL: Key ("srid")=(3819) already exists. Psql:all_data_second.sql:28821661: ERROR: duplicate key value violates unique constraint "pk_role"ĭETAIL: Key ("id")=(1731) already exists. Psql:all_data_second.sql:28818328: ERROR: duplicate key value violates unique constraint "ja_mobiusers_pkey"ĭETAIL: Key ("id")=(683341) already exists. Psql:all_data_second.sql:28810421: ERROR: duplicate key value violates unique constraint "ja_customers_pkey"ĭETAIL: Key ("id")=(338401) already exists. Psql:all_data_second.sql:26545982: ERROR: duplicate key value violates unique constraint "ja_clients_pkey" Psql:all_data_second.sql:12336660: ERROR: duplicate key value violates unique constraint "pk_tax_aggregates"ĭETAIL: Key ("tax_aggregate_id")=(634898) already exists. Psql:all_data_second.sql:10938107: ERROR: duplicate key value violates unique constraint "pk_invoices"ĭETAIL: Key ("invoice_id")=(340990) already exists. Psql:all_data_second.sql:10586440: ERROR: duplicate key value violates unique constraint "pk_bills"ĭETAIL: Key ("bill_id")=(764047) already exists. I dropped PROJECTION SCHEMA.TABLE1_UK several times but it keeps coming back.Psql:all_data_second.sql:3404263: ERROR: duplicate key value violates unique constraint "pk_billables"ĭETAIL: Key ("billable_id")=(17) already exists.
SEGMENTED BY hash(TABLE1.NCT_LINE_ID, TABLE1.NCT_NUMBER) ALL NODES KSAFE 1 FYI, this table is about 20,000 rows.ĪLTER TABLE SCHEMA.TABLE1 ADD CONSTRAINT TABLE1_PK PRIMARY KEY (NCT_NUMBER, NCT_LINE_ID) ENABLED
DBVISUALIZER UNIQUE CONSTRAINT CODE
Below is the portion of code after I exported the object. I checked both projections again and they are both on the exact same two fields. I checked the projection table and both the unsegmented projection I created and the segmented projection that the system created have is_key_constraint_projection = 'true'. Refresh completed with the following outcomes: The projection must have a sufficient number of buddy projections and all nodes must be up before starting a refresh Execute the select start_refresh() function to copy data into this projection. WARNING 4468: Projection is not available for query processing. +-ĭbadmin=> create projection pk_test_new as select * from pk_test order by c1 unsegmented all nodes Projection_name | is_key_constraint_projection WARNING 2623: Column "c1" definition changed to NOT NULLĭbadmin=> select projection_name, is_key_constraint_projection from projections where anchor_table_name = 'pk_test' If so, you can drop the segmented projection.ĭbadmin=> create table pk_test (c1 int, c2 varchar(10)) ĭbadmin=> alter table pk_test add constraint pk_test_pk primary key (c1) enabled If you have an enabled PK constraint there has to be at least one "special" Projections to enforce it.Ĭheck if the new unsegmented projection you created is one of those (in the PROJECTIONS system table, IS_KEY_CONSTRAINT_PROJECTION will be TRUE).
0 kommentar(er)
