You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2009/09/04 22:16:57 UTC
[jira] Closed: (JUDDI-275) select distinct issues -> use group by
[ https://issues.apache.org/jira/browse/JUDDI-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam closed JUDDI-275.
-----------------------------
Resolution: Fixed
done
> select distinct issues -> use group by
> --------------------------------------
>
> Key: JUDDI-275
> URL: https://issues.apache.org/jira/browse/JUDDI-275
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0beta
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.0
>
>
> When we do searches for BusinessEntities, BindingTemplates, Services and
> TModels we sort by name. However the name is not in the
> business_entity table, but rather in the business_name, because multiple
> business names can be given (for different locales). In the code we
> select the business entity and then try to sort by name. Some dbs think
> this is ok, but in fact most of them do not like it (including Derby).
> You get an error which is explained pretty well in this article:
> http://weblogs.sqlteam.com/jeffs/archive/2007/12/13/select-distinct-order-by-error.aspx
> Weshould fix this by not doing a "select distinct" but rather doing a
> "group by".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.