Ok, you are correct. I was in cross-query mode (even though I was only accessing one database). When I switched to query mode, it worked.
So help me understand what is behind this. You are saying that in cross-connect mode it is necessary to have all the SQL be MySQL compatible? Shouldn’t Toad Data Point take care of that “behind the scenes” when I bring up the Where Clause box and select Date Range – Yesterday? If not, does anyone know if this is on a future release enhancements list?
That being said, how would I handle my current scenario where I am attempting to compare a Teradata data (process_dt) to yesterday (11/10/2015)?
Is it the process_dt that needs to be converted to a MySQL format, or the literal, or both?
From: Aleksey Bazhenov [mailto:bounce-AlekseyBazhenov@toadworld.com]
Sent: Wednesday, November 11, 2015 2:03 AM
Subject: RE: [Toad Data Point - Discussion Forum] Teradata Date error in WHERE
RE: Teradata Date error in WHERE
Reply by Aleksey Bazhenov
How Toad displays dates depends on local settings. Date format in WHERE clause depends on query type. If it’s a cross-query then MySQL date/time literals have to be used in WHERE clause.
What query do you execute? It looks like it’s a cross query. So MySQL date literals should be in the WHERE clause.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad Data Point - General notifications altogether.
Toad Data Point - Discussion Forum
this post as spam/abuse.