• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: cannot update imported DB entries; can update new ones
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cannot update imported DB entries; can update new ones


  • Subject: Re: cannot update imported DB entries; can update new ones
  • From: Christian Evans <email@hidden>
  • Date: Fri, 1 Oct 2004 09:53:48 -0400

I had a similar problem when I started working with MySQL. Turned out the imported records had the date field all screwed up and although WO would load them OK for viewing, they wouldn't save even if I edited the date to correct the problem.

I had to change the import files to correct the problem and I used MySQL's command line import tools. Unfortunately, I can't remember what I did to the import files to fix it. I think I changed the format of the date from mm/dd/yyyy to something that MySQL liked better for import. After that WO worked fine.

Christian

On Sep 30, 2004, at 5:44 PM, Art Isbell wrote:

On Sep 30, 2004, at 3:12 AM, Jeremy Matthews wrote:

However, when I take an entry that I imported directly into MySQL (via CocoaMySQL), it will display and delete fine. And when I click on the "Editing" link I setup, it passes the values accordingly. But then, after changing some values, I try to save and hit a WO error message:

com.webobjects.eoaccess.EOGeneralAdaptorException: updateValuesInRowDescribedByQualifier -- com.webobjects.jdbcadaptor.JDBCChannel method failed to update row in database

This exception is generally thrown when an optimistic locking failure has occurred. I.e., the values of the attributes used for locking in the cache (i.e., the values fetched) do not match the values of the same attributes in the database when the update is being saved. This can occur when some other process has updated the object since it was fetched by your WO process or when a rounding error occurs when the database value is converted to a possibly less precise Java value. This can happen with timestamps or floating point values. You might try excluding NSTimestamp attributes from the list of attributes used for locking in your EOModel to see whether that solves the problem.


Aloha,
Art

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Prev by Date: Accessing ADS via EO
  • Next by Date: Load balancing a web service
  • Previous by thread: Accessing ADS via EO
  • Next by thread: Load balancing a web service
  • Index(es):
    • Date
    • Thread