> From: Juha Mets?kallas <[EMAIL PROTECTED]>
> Date: Wed, 01 Nov 2006 07:54:18 +0200
Hi Metsis,
> Hello
>
> There has been some postnings about locking and conflict resolving in
> databases. Being rather newbie with databases in RB environment (having
> experience mostly with Interbase accessed through Delphi), I like to
> hear more about this topic. To specify, I mean by conflict resolving how
> the database supports detecting/preventing the situation where two users
> (user 1 and user 2 in that order) have read same data (possibly JOINed
> from several tables), modified it and commit the changes so that other's
> modifications would be lost if nothing is done.
>
> An app using SQLite (REALdatabase) which is a pure single user database,
> can be designed so that this is not an issue with it. Same applies to
> embedded Valentina.
>
> IIUC, REALSQLDatabase uses locking on some level with no built-in
> support on conflict resolving. How does this locking happens, though a
> table or query component? How do Mysql, PostgreSQL and Valentina behave?
>
> Answers or pointers appreciated.
You ask questions which are described on many pages :-)
May be simply better read docs of each db if you want know how each works.
In short about Valentina:
* Valentina use true record level locks.
* when you build cursor you can spend what cursor you want:
- serverside or clientside
- nolocks, readonly, readwrite locks
- forward only, random.
--
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]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
