Public bug reported:
When I run aggregate queries, this creates start dates and end dates
based on specific reporting dates irrespective of period types. For
example, a monthly period type start date and end date could be
2014-03-20. This is creating conflicts when you try to run analytics
there is an error:
* ERROR 2014-04-28 22:58:07,734 Unexpected error occurred in scheduled task.
(TaskUtils.java [taskScheduler-1])
org.springframework.dao.DuplicateKeyException: PreparedStatementCallback; SQL
[insert into _periodstructure values (?,?,?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR:
duplicate key value violates unique constraint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.; nested exception is
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constr
aint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value
violates unique constraint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.
I wasn't getting these errors before using earlier 2.15 builds.
Is there an easy way to sort this out apart from deleting the periods in
the period table (which takes care of the problem but not entirely sure
what the long term implications are)?
Many thanks
Busoye
Version:
2.15
Build revision:
14960
** Affects: dhis2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1313954
Title:
conflicting period structures generated by aggregate queries
Status in DHIS 2:
New
Bug description:
When I run aggregate queries, this creates start dates and end dates
based on specific reporting dates irrespective of period types. For
example, a monthly period type start date and end date could be
2014-03-20. This is creating conflicts when you try to run analytics
there is an error:
* ERROR 2014-04-28 22:58:07,734 Unexpected error occurred in scheduled task.
(TaskUtils.java [taskScheduler-1])
org.springframework.dao.DuplicateKeyException: PreparedStatementCallback; SQL
[insert into _periodstructure values (?,?,?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR:
duplicate key value violates unique constraint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.; nested exception is
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constr
aint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value
violates unique constraint "in_periodstructure_iso"
Detail: Key (iso)=(201403) already exists.
I wasn't getting these errors before using earlier 2.15 builds.
Is there an easy way to sort this out apart from deleting the periods
in the period table (which takes care of the problem but not entirely
sure what the long term implications are)?
Many thanks
Busoye
Version:
2.15
Build revision:
14960
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1313954/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
