incubator-connectors-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby
Date Sat, 02 Apr 2011 12:00:05 GMT


Karl Wright commented on CONNECTORS-110:

This ticket is stalled because it requires a new Derby feature to resolve.  The resolution
will be to assess the current version of Derby and find out whether the required feature has
been added, and barring that, opening a Derby ticket for the feature.

> Max activity and Max bandwidth reports don't work properly under Derby
> ----------------------------------------------------------------------
>                 Key: CONNECTORS-110
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework crawler agent
>            Reporter: Karl Wright
> The reason for the failure is because the queries used are doing the Postgresql DISTINCT
ON (xxx) syntax, which Derby does not support.  Unfortunately, there does not seem to be a
way in Derby at present to do anything similar to DISTINCT ON (xxx), and the queries really
can't be done without that.
> One option is to introduce a getCapabilities() method into the database implementation,
which would allow ACF to query the database capabilities before even presenting the report
in the navigation menu in the UI.  Another alternative is to do a sizable chunk of resultset
processing within ACF, which would require not only the DISTINCT ON() implementation, but
also the enclosing sort and limit stuff.  It's the latter that would be most challenging,
because of the difficulties with i18n etc.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message