On Thu, May 25, 2006 at 14:56:51 -0700,
operationsengineer1@yahoo.com wrote:
>
> Bruno,
>
> This looks like it does what i want...
>
> SELECT DISTINCT ON (t_inspect_result.inspect_id)
> t_inspect_result.inspect_id,
> t_inspect_result.inspect_result,
> t_inspect_result.inspect_timestamp
> FROM t_inspect_result, t_inspect, t_inspect_area,
> t_serial_number,
> t_link_contract_number_job_number, t_job_number,
> t_product
> WHERE t_inspect.inspect_area_id =
> t_inspect_area.inspect_area_id
> AND t_inspect.serial_number_id =
> t_serial_number.serial_number_id
> AND t_serial_number.link_contract_number_job_number_id
> =
>
> t_link_contract_number_job_number.link_contract_number_job_number_id
> AND t_link_contract_number_job_number.job_number_id =
> t_job_number.job_number_id
> AND t_product.product_id =
> t_job_number.product_id
> AND t_inspect.inspect_id =
> t_inspect_result.inspect_id
> AND t_inspect.serial_number_id = '184'
> ORDER BY t_inspect_result.inspect_id DESC,
> t_inspect_result.inspect_timestamp DESC
> -- inspect_id desc impacts end result. time desc
> -- impacts the groups prior to being distinctly listed
>
> as you can see in the note, the timestamp DESC works
> within the groups, not on the single group value
> ultimately returned (as it should). how can i get it
> to work on returned groups, too? i work around it by
> putting inspect_id in desc order (they typically occur
> one after another), but that may not always work.
It would be nice to see some sample data, output and explains.