If a date argument for the node creation date is used an additional join on the node table is performed causing the views results to be messed up.

This happens in Date 2.6, reverting to Date 2.4 fixes the issue.

CommentFileSizeAuthor
#1 date-904146-1.patch682 bytesplach

Comments

plach’s picture

Status: Active » Needs review
StatusFileSize
new682 bytes

The problem seems to be in the newly added date_api_argument_handler::set_relationship() method which adds the needed tables to the query table queue without checking if they are already there.

The attached patch fixes the reported issue, I ain't sure some more check is needed to make everything work as intended.

MichaelP’s picture

karens’s picture

Status: Needs review » Needs work

This part of the code has changed and I'm not clear if this still is needed. I'm also not sure this is going to work right if there is a relationship, i.e. we need one table for the original node and another for a node provided by a relationship. In that case we *do* need another join.

damienmckenna’s picture

Component: Date CCK Field » Code
Issue summary: View changes
Status: Needs work » Closed (won't fix)

Unfortunately the D6 version of this module is no longer supported, but we appreciate the time you put into this. If this problem is relevant for D7 too, please reopen the issue. Thanks.