Hi,

>Oh, my goodness, who told you that the whole table
>will be locked for the query with WHERE ID = 123456 ?

Oops, I forgot to tell you that I set isolation level to serializable, a
pologies. It's because I decided to, after two years of database work,
finally really understand how things work :-/ I think I more / less do now.

Something that I found interesting is that if primary keys would be
immutable, SELECT/UPDATE .... WHERE ID = 123456 could lock a single row and
still maintain serializable isolation level. This could be extended to
foreing keys. On second thought, this is a degenerated form of predicate
locks.


>We will check here if it is easy to allow SQLStudio to
>handle select direct.

Well, I wouldn't bother... For SQLStudion trigger/dbproc editor is would be
something...


>But as I told you (and it is written in the archive ones
>or twice, therefore I thought you may have read this) with
>the next major release select direct will not exist any more.

You spend a lot of your valuable time just telling people to RTFM. Do you
have control over http://www.sapdb.org/sap_db_FAQ.htm, or is it
responsibility of some other division of SAP? I'd be happy to contribute
content, and an application to maintain it, if needed.


Best regards,
Wojtek



_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to