Strange behaviour in Views using Date argument and "Node: Post Date"

I did it right now, tested it, the situation is still the same. Might an export of my view be of any help?

Seems identical to what I have. WHen you give the argument, do you pass it as YYYY-MM-DD ?

I call my page this way:

http://mysite.com/myview/2010-10-13

It seems like working if I use Node Revision: Created as an argument. But i.e. doesn't work with the Node Updated date.

Setting the date argument as Node: Updated (granularity Day) and Calling:

www.mysite.com/myview/2010-10-13

gives me also a result for a node which was updated 2010-10-12. This is proved by the use of the Node: Updated date Field, which is clearly outputting 2010-10-12.

Maybe I should turn this to a bug report

The mistake seems to be located in the generated query.
To reproduce simply create a view, add Node: Title as a field and a Date(Node) as an argument. Pick node(updated date) as date field and "Day" as granularity. Then run the view passing as argument the value 2010-10-12... It will generate this query:

SELECT DISTINCT(node.nid) AS nid,
   node.title AS node_title,
   node.language AS node_language
 FROM node node 
 LEFT JOIN node node2 ON node.tnid = node2.tnid
 WHERE (DATE_FORMAT(ADDTIME(FROM_UNIXTIME(node2.changed), SEC_TO_TIME(7200)), '%Y-%m-%%d') <= '2010-10-12' AND DATE_FORMAT(ADDTIME(FROM_UNIXTIME(node2.changed), SEC_TO_TIME(7200)), '%Y-%m-%%d') >= '2010-10-12')
 GROUP BY nid

This query is wrong and returns ALL THE NODES as soon as it finds some node which was updates in that date!

The correct query would be this one:

SELECT DISTINCT (
node.nid
) AS nid, node.title AS node_title, node.language AS node_language
FROM node
WHERE (
DATE_FORMAT( ADDTIME( FROM_UNIXTIME( node.changed ) , SEC_TO_TIME( 7200 ) ) , '%Y-%m-%d' ) <= '2010-10-12'
AND DATE_FORMAT( ADDTIME( FROM_UNIXTIME( node.changed ) , SEC_TO_TIME( 7200 ) ) , '%Y-%m-%d' ) >= '2010-10-12'
)
GROUP BY nid
LIMIT 0 , 30

I'm not sure I'm able to patch it, but I'll give it a try

interesting update: if I use the node revision: Created Date filter, the bug doesn't appear: the SQL code is in facts correct (see below).

SELECT DISTINCT(node.nid) AS nid,
node.title AS node_title
 FROM node node 
 LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid
 WHERE (DATE_FORMAT(ADDTIME(FROM_UNIXTIME(node_revisions.timestamp), SEC_TO_TIME(7200)), '%Y-%m-%%d') <= '2010-10-11' AND DATE_FORMAT(ADDTIME(FROM_UNIXTIME(node_revisions.timestamp), SEC_TO_TIME(7200)), '%Y-%m-%%d') >= '2010-10-11')
 GROUP BY nid

Unfortunately for my application is trivial to select only nodes filtered by updated date and a range (which is the reason to use DateAPI instead of the standard Node: Updated Date field).
If there is something I can look in to help please let me know, thanks

Interesting... I also pasted code from a newly created view.

The presence of this in my code:

LEFT JOIN node node2 ON node.tnid = node2.tnid

is probably related to translations/multilingual system (it checks tnid). Do you make use of locale / i18n?

However I'm going to try it in a fresh install and see what comes out.

I confirm that the bug appears when the Content translation module is enabled. Unfortunately I have no idea where to get started to work on it, where is the problem born? In DateAPI, in Views, in Content translation?

Some workaround using relationships?

The bug is blocking for anyone needing to use DateAPI arguments in a multilingual site.

I think those are not workarounds for anyone using a multilingual site. Also, I need to use date range features (like 2009-12-20--@).
If someone has some hints about how to get started fixing this, would be appreciated