Activity #3613
closed
as of now no lg_code in mas_lsg table matches with the lg_code in mas_village
- Status changed from New to Feedback
as of now no lg_code in mas_lsg table matches with the lg_code in mas_village. so as of now the entire village is being listed.
Create a table mapping village and lsg as follows :
CREATE TABLE public.mas_village_lsg_mapping (
village_id INTEGER NOT NULL,
lsg_id INTEGER NOT NULL,
last_chg_by INTEGER,
last_chg_dt TIMESTAMP WITHOUT TIME ZONE DEFAULT now(),
status VARCHAR DEFAULT 'y'::character varying,
CONSTRAINT mas_village_lsg_mapping_pkey PRIMARY KEY,
CONSTRAINT fk_mas_village_lsg_village_id FOREIGN KEY (village_id)
REFERENCES public.mas_village(village_id)
ON DELETE NO ACTION
ON UPDATE NO ACTION
NOT DEFERRABLE,
CONSTRAINT fk_ph_ward_village_last_chg_by FOREIGN KEY (last_chg_by)
REFERENCES public.users(user_id)
ON DELETE NO ACTION
ON UPDATE NO ACTION
NOT DEFERRABLE
) ;
ALTER TABLE public.mas_village_lsg_mapping
OWNER TO postgres;
Import data for the table
Attached...change schema name from public to dp. and make changes to insert sctipt as needed for import.
Use the village-lsg mapping table for filtering villages based on selected LSG.
- Status changed from Feedback to In Progress
Data level correction to map district ID of village-lsg table
- % Done changed from 0 to 90
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Also available in: Atom
PDF