Why does this simple ejb-ql cause Jboss4.0.3 to complain LEX

[natgross]

Hi;
Please point out the error in the seemingly simple query. Jboss 4.0.3 will not deploy this jar file due to the the following ejb-ql:

<ejb-ql>[CDATA[SELECT OBJECT(qqq) FROM Pq as qqq WHERE qqq.timeStart < "2005-01-01"]]</ejb-ql>

And a partial trace upon deployment is:

20:50:53,695 INFO [STDOUT] org.jboss.ejb.plugins.cmp.ejbql.TokenMgrError: Lexical error at line 1, column 57. Encountered: "\"" (34), after : ""
20:50:53,697 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParserTokenManager.getNextToken(EJBQLParserTokenManager.java:1775)
20:50:53,697 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.getToken(EJBQLParser.java:4199)
20:50:53,697 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_3R_12(EJBQLParser.java:3193)
20:50:53,697 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_3_2(EJBQLParser.java:3228)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_2_2(EJBQLParser.java:2793)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.ConditionalPrimary(EJBQLParser.java:820)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.ConditionalTest(EJBQLParser.java:789)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.ConditionalFactor(EJBQLParser.java:766)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.WhereConditionalTerm(EJBQLParser.java:613)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.WhereExpression(EJBQLParser.java:568)
20:50:53,698 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.WhereClause(EJBQLParser.java:532)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.EJBQL(EJBQLParser.java:117)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.parse(EJBQLParser.java:65)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.EJBQLToSQL92Compiler.compileEJBQL(EJBQLToSQL92Compiler.java:96)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc2.EJBQLQueryCommand.<init>(EJBQLQueryCommand.java:34)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc2.QueryFactory.init(QueryFactory.java:101)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.startStoreManager(JDBCStoreManager2.java:441)
20:50:53,699 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.start(JDBCStoreManager2.java:187)
20:50:53,700 INFO [STDOUT] at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)

Thank you much.
-nat

[oglueck]

Is timeStart a string? If not, use a parameter to pass in a Date. If yes, the string constant should be in single quotes. And I doubt the Object cast is necessary.

[natgross]

timeStart is a TimeStamp. So the only way for date-time types to be compared is via a parameter?
Can I compare a date type (wether TimeStamp or sql.Date) with null, hardcoded?
Like this: WHERE qqq.timeStart IS NULL
or WHERE qqq.timeStart=null
(I just checked the data itself, and have many cases of null in this field.)
Thank you!
-nat

[natgross]

(Please excuse my 2 login profiles here. I had thought my original profile was lost. Different stations/browsers are keeping different logons/passwords, and keeping me busy!)
-nat

[oglueck]

Hey, why don't you read the specs? All your questions are answered there.

For the record: it's "field IS NULL" and no there is no way to have date/time constants.

[natgross]

I thought I memorized the specs. It seems like I didn't:).
Thank you much!
-nat