[
http://mifosforge.jira.com/browse/MIFOS-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock updated MIFOS-2851:
--------------------------------
select child.customer_id, child.status_id as status, child.display_name,
child.customer_level_id as Level,
child.parent_customer_id, parent.status_id as ParentStatus,
parent.display_name as ParentDisplayName, parent.customer_level_id as
ParentLevel,
childcm.meeting_id as ChildMeetingId, childm.meeting_place,
childrd.recur_after, childr.days,
parentcm.meeting_id as ParentMeetingId, parentm.meeting_place,
parentrd.recur_after, parentr.days
from customer child
join customer_meeting childcm on childcm.customer_id = child.customer_id
join meeting childm on childm.meeting_id = childcm.meeting_id
left join recurrence_detail childrd on childrd.meeting_id = childm.meeting_id
left join recur_on_day childr on childr.details_id = childrd.details_id
join customer parent on parent.customer_id = child.parent_customer_id
join customer_meeting parentcm on parentcm.customer_id = parent.customer_id
join meeting parentm on parentm.meeting_id = parentcm.meeting_id
left join recurrence_detail parentrd on parentrd.meeting_id = parentm.meeting_id
left join recur_on_day parentr on parentr.details_id = parentrd.details_id
where childm.meeting_id <> parentm.meeting_id
and (childm.meeting_place = parentm.meeting_place and childrd.recur_after =
parentrd.recur_after and childr.days = parentr.days)
order by parent.customer_id
The above query is a slight alteration to the main find problem query. It is
to see which 'old' meetings have been set to the 'new' meeting and still
remain so. (item (2) above)
In secdep (Van's version) there were 69 customers whose meeting_id (old
meeting) was different to their parents. And 60 of the old meetings matched
the new meeting exactly.
In GK (Sungards copy ... up to 31/01/2010) there were 21 customers whose
meeting_id (old meeting) was different to their parents. and 13 of the old
meetings matched the new meeting exactly.
> Clean up data falling out from Issue 2652
> -----------------------------------------
>
> Key: MIFOS-2851
> URL: http://mifosforge.jira.com/browse/MIFOS-2851
> Project: mifos
> Issue Type: Bug
> Components: Centers
> Affects Versions: Gazelle C
> Reporter: Kay Chau
> Assignee: Adam Monsen
> Priority: Major
>
> As a result of Issue 2652, opening a separate issue to track the cleaning up
> of existing bad data as a result of the issue
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
