You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2009/08/13 11:01:14 UTC
[jira] Commented: (LANG-358) ObjectUtils.coalesce
[ https://issues.apache.org/jira/browse/LANG-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742774#action_12742774 ]
Henri Yandell commented on LANG-358:
------------------------------------
Ponders coalesce vs 'firstNotNull'.
Interesting that the first doc I found on SQL coalesce uses firstNotNull as the label:
http://msdn.microsoft.com/en-us/library/ms190349.aspx
> ObjectUtils.coalesce
> --------------------
>
> Key: LANG-358
> URL: https://issues.apache.org/jira/browse/LANG-358
> Project: Commons Lang
> Issue Type: New Feature
> Reporter: Jörg Gottschling
> Priority: Minor
> Fix For: 3.0
>
> Attachments: ObjectUtils.java, ObjectUtilsTest.java
>
>
> I like to see the coalesce-function from SQL implemented in ObjectUtils. Something like this:
> <T> T ObjectUtils.coalesce(T... t)
> The first object, which is not null will be returned. This would replace all the defaultValue/defaultString/... methods, with al flexibler and shorter method. It will also reuse an existing name.
> I think it's simple. Perhaps there should be overloading methods with fixed parameter sizes. Following the jdk this seems to a little faster:
> <T> T ObjectUtils.coalesce(T t1, T t2)
> <T> T ObjectUtils.coalesce(T t1, T t2, T t3)
> ...
> I would provide it, including tests, if you like.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.