| From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
|---|---|
| To: | Philippe Lang <philippe(dot)lang(at)attiksystem(dot)ch> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Delphi 2005, Postgresql, ZEOS & optimistic locking |
| Date: | 2005-05-12 19:07:06 |
| Message-ID: | 4283A95A.5030706@amsoftwaredesign.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Why not just add a onenter event handler to the forms field in question and just check the data before they edit it.
If it's different update the field with the most current data.
Access probably just does something similar under the hood for you.
I don't think that's a feature of the ODBC driver or is it?
If it is you could always use the ODBC driver from Delphi as well.
>
> With Dephi/BDE/ODBC, this is different: as soon as you try updating a field that has been modified by someone else meanwhile, the field is automatically updated for you before you start making your own changes, and of course before you try to commit them. That's fine too. I would have preferred an error personnally.
>
> Is there a way to do the same with ZEOS? Or maybe is there another mecanism that could be used to do optimistic locking? Some kind of "long transactions", in the database server?
>
> Philippe Lang
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ralf Schuchardt | 2005-05-12 19:12:35 | Re: Delphi 2005, Postgresql, ZEOS & optimistic locking |
| Previous Message | Jimmie H. Apsey | 2005-05-12 19:00:50 | Re: pg_dump fails on 7.4 Postgres |