API vs SQL vs Classes

[Ruslan Zasukhin]

On 30/3/07 8:09 AM, "Kim Kohen" <kim at webguide.com.au> wrote:

Hi Kim,

> G'day Ruslan,
> 
>> You need use for first cursor - NoLocks.
>> If result is small, you can use Client/side cursor
>>     (note, e.g. MySQL have only such cursor)
>> In this case all found records are copied to RAM of client computer,
>> And on locks are set of server side. So your following
>>   UPDATE
>>     or second cursor (server-side)
> €€€€
> All this aside, I can still choose to do a straight SQL insert and
> the locks won't stop me, correct? I'm thinking if I make the main
> list read only and all the editable areas straight SQL it might be
> easier to manage.

INSERT do not care about existed locks, because it INSERT a new record.

But UPDATE do care of course.

> Of course that may require some sort of locking system to be built
> into the application but how hard can that be?  :)

I think not a good idea

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]