I am suddenly getting strange optimistic locking failures when when updating a row on ec.saveChanges(). At least it seems sudden to me because I can't introspect well enough to see where I caused it. :-) I'm seeing this.
Jun 10 15:14:02 eTimesheet[55555] INFO er.transaction.adaptor.Exceptions - Database Exception occured: com.webobjects.eoaccess.EOGeneralAdaptorException: updateValuesInRowDescribedByQualifier -- com.webobjects.jdbcadaptor.JDBCChannel method failed to update row in database. So, I logged at the SQL and capture the userInfo() on the exception. What really caught my eye is the update statement that was produced. The WHERE statement makes it seem like is locking on every attribute in the PERSON entity. My model definitely does not reflect that should be happening. UPDATE PERSON SET campus_mail_code = ?, should_sync = ?, person_first_name = ?, start_end_date = ?, norm_vac_max = ?, student_status = ?, start_begin_date = ?, campus_phone = ?, home_dept_code = ?, person_middle_name = ?, email_address_other = ?, emp_status = ?, work_addr_line2 = ?, emp_rel_code = ? WHERE (person_id = ? AND modify_date = ? AND comp_time_bal = ? AND emergency_info = ? AND emp_rel_code = ? AND norm_vac_max is NULL AND out_of_office = ? AND pto_hrs_bal = ? AND sick_lv_hrs_bal = ? AND start_begin_date is NULL AND start_end_date is NULL AND start_percent = ? AND vac_hrs_balance = ? AND work_addr_city is NULL AND work_addr_line1 = ? AND work_addr_line2 is NULL AND work_addr_state is NULL AND work_addr_zip is NULL) Can anyone help explain the abnormal growth of my WHERE clause? Tim UCLA GSE&IS
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
