[appengine-java] Re: UnsupportedDatastoreFeatureException

2009-11-04 Thread IlyaE
Ok i figured it out now. I was trying to refer to the classname ContactInfo in my filter rather than the object name in my User class contactInfo. The difference in case for the leading 'C' was the culprit. On Nov 4, 10:19 am, IlyaE wrote: > If i change my authenticate filter to >              

[appengine-java] Re: UnsupportedDatastoreFeatureException

2009-11-04 Thread IlyaE
If i change my authenticate filter to query.setFilter("ContactInfo.email == emailParam && password == passwordParam"); I now get this error. javax.jdo.JDOUserException: Identifier ContactInfo.email is unresolved (not a static field) On Nov 3, 9:32 pm, "Max Ross (Google)" wrot

[appengine-java] Re: UnsupportedDatastoreFeatureException

2009-11-03 Thread Max Ross (Google)
Andy has pinpointed the issue. You most likely don't have a field on your MyUser class named "email" but the error isn't being triggered on the first query because your second call to setFilter() is overwriting the reference to the nonexistent field. You'll need to pass the entire filter to setfi

[appengine-java] Re: UnsupportedDatastoreFeatureException

2009-11-03 Thread datanucleus
Multiple calls to setFilter will overwrite the previous value. Do you really want to do that? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to go