Re: What is the locking in EOModeler

Hi,

Thank you a lot for your response. I have read your documentations  
and I have observed that the error came because a locking was set on  
a Timestamp saved as date in our PostgreSQL database. When the update  
was checked, EOF receive a message that 0 row was updated because it  
compares a date without time, with a Timestamp has time.

I don't understand Randy who says that he doesn't put any lock in  
nullable fields. Has the update request always made with the primary  
key, we are sure that all the records with null fields aren't be  
affected.
Anyone knows why we can put a lock on the primary key? Isn't it  
always in the "where close" update request and what will in change?

Thank you,

Simon

Le 9 mai 06 à 16:35, David LeBer a écrit :

> On 9-May-06, at 10:21 AM, FRANSSEN Simon wrote:
>
>> Hi,
>>
>> I have a problem, when I doing a few big modifications in a  
>> database, it's crashing! But When I "click off" the locking in  
>> EOModeler, it's working! Does anyone knows what is the exact  
>> utility of this locking and why the application "crashed" during  
>> the saving of the modifications?
>
> The lock icon in EOModeler indicates that optimistic locking is  
> enabled for that attribute.
>
> You're post is a little light on details, but I would assume that  
> you are encountering an optimistic locking error when trying to save.
>
> Optimistic locking: <http://developer.apple.com/documentation/ 
> LegacyTechnologies/WebObjects/WebObjects_5/Topics/ProgrammingTopics. 
> 2c.html>
>
> EOModeler: <http://developer.apple.com/documentation/WebObjects/ 
> UsingEOModeler/index.html>
>
> Some information that might help track down your issue:
>
> - Database type and version.
> - Attribute type suffering the locking failure.
> - Stack trace of the error.
>
> --
> ;david
>
> --
> David LeBer
> Codeferous Software
> 'co-defer-ous' adj. producing or containing code
> site:   http://www.codeferous.com
> blog: http://david.codeferous.com
>
>
>
>