• 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: D2W locking error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: D2W locking error


  • Subject: Re: D2W locking error
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 1 Dec 2010 18:09:25 -0800

On Dec 1, 2010, at 6:06 PM, Andrew R. Kinnie wrote:

> I don't know what InnoDB is, so I'd have to say no.

I don't use MySQL.  But I do know that MySQL without InnoDB is... not something I would trust data to.  Check the Wiki or search for posts on this by Kieran.


>  I did delete all the bookings and add new ones.  No change.  :-/
>
> The bookings for the feature are still not appearing either, even though they are new, but I assume that's a different issue.

Could be lack of InnoDB, but more likely something wrong in your app or model.


Chuck



>
> On Dec 1, 2010, at 9:01 PM, Chuck Hill wrote:
>
>> On Dec 1, 2010, at 5:58 PM, Andrew R. Kinnie wrote:
>>> On Dec 1, 2010, at 8:42 PM, Chuck Hill wrote:
>>> On Dec 1, 2010, at 5:35 PM, Andrew R. Kinnie wrote:
>>>>
>>>>> Hmm.  That was checked, but set as false.  In any event, I was using an auto-increment.  I gather I should remove this?  EOF will do the right thing and create it's own pk?
>>>>
>>>> Yes.  Auto-increment does not mix well with data created from  EOF.
>>>>
>>>>
>>>>> I changed the debug enabled to true and got this in the console when I tried to delete a duplicate:
>>>>
>>>>> ...
>>>>> SELECT t0.AGENT_ID, t0._rowid, t0.COMIC_ID FROM BOOKING t0 FOR UPDATE
>>>>> ...
>>>>>
>>>>
>>>>
>>>> That is a pretty clear sign that EOF is visibly upset.  :-)  See if removing the auto-increment helps.
>>>>
>>>
>>> I already tried that and it didn't help.  :-/
>>>
>>> Of course now the other issue is that the bookings for the feature act are not showing up at all.
>>>
>>> This is a new site.  Am I better off just deleting all the bookings and adding new ones?  (there's only about 25 of them)
>>
>>
>> That is worth a try.  If you created data with auto-increment and don't have the FK constraints enforced in the database, the relationships might be broken (bad data).
>>
>> Are you running MySQL with InnoDB?
>>
>>
>> Chuck
>>
>> --
>> Chuck Hill             Senior Consultant / VP Development
>>
>> Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
>> http://www.global-village.net/products/practical_webobjects
>>
>>
>>
>>
>>
>>
>>
>

--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

  • Follow-Ups:
    • Re: D2W locking error
      • From: "Andrew R. Kinnie" <email@hidden>
References: 
 >D2W locking error (From: "Andrew R. Kinnie" <email@hidden>)
 >Re: D2W locking error (From: Chuck Hill <email@hidden>)
 >Re: D2W locking error (From: "Andrew R. Kinnie" <email@hidden>)
 >Re: D2W locking error (From: Chuck Hill <email@hidden>)
 >Re: D2W locking error (From: "Andrew R. Kinnie" <email@hidden>)
 >Re: D2W locking error (From: Chuck Hill <email@hidden>)
 >Re: D2W locking error (From: Chuck Hill <email@hidden>)
 >Re: D2W locking error (From: "Andrew R. Kinnie" <email@hidden>)

  • Prev by Date: Re: D2W locking error
  • Next by Date: Re: D2W locking error
  • Previous by thread: Re: D2W locking error
  • Next by thread: Re: D2W locking error
  • Index(es):
    • Date
    • Thread