[
https://issues.apache.org/jira/browse/CONFIGURATION-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844299#comment-17844299
]
pieter martin commented on CONFIGURATION-845:
---------------------------------------------
The order information is lost. In my case one could order by the primary
sequence but that would not be a generic solution.
All I can think is to hide, the order in the list, in the value itself and
post-process and sort the values.
Or an additional column to carry the order information.
I don't think it should be optional as downstream clients might rely on a List
being a list with a determined order.
> DatabaseConfiguration loses list property's order
> -------------------------------------------------
>
> Key: CONFIGURATION-845
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-845
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 2.10.1
> Reporter: pieter martin
> Priority: Major
>
> {code:java}
> private static final String SQL_GET_PROPERTY = "SELECT * FROM %s WHERE %s =?";
> {code}
> This is the query DatabaseConfiguration executes to get a property's values.
> It assumes the order will be insertion order but this is not true on
> postgresql.
> So configuration.getList(key) loses the order of the list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
