Everything is passing again w/o any changes. Looks like it was just a timing issue....
-Donald On 2/13/10 10:02 PM, Patrick Linskey wrote: > What's the failure? > > 1509 is much more likely than 1507, as it's a change to allow enums to > be assigned in bulk updates. It's within the realm of reason that JPQL > forbids such assignments -- I didn't check, and just assumed that the > lack of enum support was a holdover from the 1.4 days. > > IMO, if that turns out to be the case, we should permit some sort of > option to enable enum modifications in bulk updates. > > > 1507 is just a NPE check that should never be null in a JDBC configuration. > > -Patrick > > On Feb 13, 2010, at 10:43 AM, Donald Woods wrote: > >> Some change in the last day is causing a 1.0b TCK regression on trunk. >> When I get a chance, I'll try backing out the changes for 1509 or 1507 >> and see which one caused it..... >> >> >> -Donald >
