ER Replication table defintion

Posted in 2012

Topics: Triggers, Constraints & Referential Integrity

FRANK — Tue, 24 Jul 2012 15:19:12 — source: IIUG Forums & Mailing Lists

Hi, Any negative impacts or potentital worry there? 15:13:39 Warning - Table noaa:informix.ds_head_nr is replicated and contains a unique index rather than a unique constraint. 15:13:39 Unique constraints should be used with replicated tables rather than a simple unique index. Thanks, Frank --bcaec51a758e552ee304c594e2aa

↪ replying to FRANK

FRANK — Tue, 24 Jul 2012 15:29:18 — source: IIUG Forums & Mailing Lists

Sorry, Give more info. Thanks, Frank IDS11.50 FC8 Table, { TABLE "informix".ds_head_nr row size = 579 number of columns = 13 index size = 319 } create table "informix".ds_head_nr ( inventory_id serial not null , dataset_name varchar(255,44) not null , dataset_size_bytes int8, datatype_name char(10) not null , datatype_version char(10), ingest_status char(10), ingest_dt datetime year to second not null , orig_data_filenm varchar(255,44) not null , distribution_site char(1) not null , data_source char(10), has_visual_file char(1), restriction_level smallint, accessible char(1), primary key (inventory_id) constraint "informix".ds_head_nr_pk ); revoke all on "informix".ds_head_nr from "public" as "informix"; create unique index "informix".ds_head_nr_idx0 on "informix".ds_head_nr (dataset_name) using btree ; create index "informix".ds_head_nr_idx2 on "informix".ds_head_nr (datatype_name) using btree ; create index "informix".ds_head_nr_idx3 on "informix".ds_head_nr (datatype_version) using btree ; create index "informix".ds_head_nr_idx4 on "informix".ds_head_nr (ingest_dt) using btree ; alter table "informix".ds_head_nr add constraint (foreign key (datatype_name) references "informix".datatypes constraint "informix".ds_head_nr_dtn); alter table "informix".ds_head_nr add constraint (foreign key (datatype_version) references "informix".datatyp_vers constraint "informix".ds_head_nr_dtv); alter table "informix".ds_head_nr add constraint (foreign key (distribution_site) references "informix".distribution_sites constraint "informix".ds_head_nr_fk1); On Tue, Jul 24, 2012 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote: > Hi, > > Any negative impacts or potentital worry there? > > 15:13:39 Warning - Table noaa:informix.ds_head_nr > > is replicated and contains a unique index > > rather than a unique constraint. > 15:13:39 Unique constraints should be used with replicated tables > > rather than a simple unique index. > > Thanks, > Frank > > --bcaec51a758e552ee304c594e2aa > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --90e6ba6136b8719cca04c59506f4

↪ replying to FRANK

Madison Pruet — Tue, 24 Jul 2012 15:53:24 — source: IIUG Forums & Mailing Lists

With unique constraints, we can do deferred constraint checking. I'm pretty sure that with recent releases we treat unique indexes as a uniq= ue constraint by the ER apply. From: "FRANK" <yunyaoqu@gmail.com> To: ids@iiug.org, Date: 07/24/2012 09:27 AM Subject: ER Replication table defintion [27798] Sent by: ids-bounces@iiug.org Hi, Any negative impacts or potentital worry there? 15:13:39 Warning - Table noaa:informix.ds_head_nr is replicated and contains a unique index rather than a unique constraint. 15:13:39 Unique constraints should be used with replicated tables rather than a simple unique index. Thanks, Frank --bcaec51a758e552ee304c594e2aa ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

↪ replying to Madison Pruet

FRANK — Tue, 24 Jul 2012 22:59:38 — source: IIUG Forums & Mailing Lists

Thanks, Madison! On Tue, Jul 24, 2012 at 11:53 AM, Madison Pruet <mpruet@us.ibm.com> wrote: > With unique constraints, we can do deferred constraint checking. I'm > pretty sure that with recent releases we treat unique indexes as a uniq= > ue > constraint by the ER apply. > > From: "FRANK" <yunyaoqu@gmail.com> > To: ids@iiug.org, > Date: 07/24/2012 09:27 AM > Subject: ER Replication table defintion [27798] > Sent by: ids-bounces@iiug.org > > Hi, > > Any negative impacts or potentital worry there? > > 15:13:39 Warning - Table noaa:informix.ds_head_nr > > is replicated and contains a unique index > > rather than a unique constraint. > 15:13:39 Unique constraints should be used with replicated tables > > rather than a simple unique index. > > Thanks, > Frank > > --bcaec51a758e552ee304c594e2aa > > ***********************************************************************= > ******** > > Forum Note: Use "Reply" to post a response in the discussion forum. > > = > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf30223f09f55fa904c59b50c9