Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
ERROR: Invalid relational operator...comparing dates
Yes, you found the original error. This query was assigned to a string variable as part of a piece of javascript. I'm building reports in Eclipse BIRT 2.3.2. And I was testing the SQL and neglected to remove some javascript variables that dynamically build the where clause. And how sad that...- AKSmith
- Post #14
- Forum: Oracle: All versions
-
ERROR: Invalid relational operator...comparing dates
Thanks for your replies. Yes, that did answer my (second) question.- AKSmith
- Post #7
- Forum: Oracle: All versions
-
ERROR: Invalid relational operator...comparing dates
Mufasa, I found an error above, sorry I know it's somewhat convoluted. Here's my other question. Why am I getting an error "not a valid month" on the following? select pm.nextdate from pm where pm.nextdate >= '12/1/2010' and pm.nextdate <= '12/31/2010'- AKSmith
- Post #3
- Forum: Oracle: All versions
-
ERROR: Invalid relational operator...comparing dates
Getting the error ORA-00920: invalid relational operator on the following query. What am I doing wrong? (select 'Next PM' as pmtype, nvl(pm.location,asset.location) as location, pm.assetnum, asset.description as assetdescr, pm.pmnum, pm.description, pm.nextdate as pmduedate, pm.jpnum...- AKSmith
- Thread
- Replies: 13
- Forum: Oracle: All versions
