A bit OT: handling multiple users in DB

Luis luis at anachreon.co.uk
Mon Sep 22 10:47:45 EDT 2008


Hiya,

It depends on what your concern is: Do you want to allow them both  
write access?

If they both have the ability to write, then the last to write will  
be the one visible - This is the standard behaviour.
If you want to ensure only one is able to update a field then you  
lock down their access.

If you plan on the need for a rollback, for whatever reason, then you  
might as well implement a tracking option to list all the changes (I  
do this for accountability, not for data restore).

Cheers,

Luis.


On 22 Sep 2008, at 15:36, Klaus Major wrote:

> Hi Luis,
>
>> Hiya,
>>
>> I suppose you could have a column for each, and each entry tagged  
>> with the user ID and time.
>> If both values need to be shown you could display the data for  
>> both on a table showing the change and the time it was committed.
>
> Yes, I found a similar solution on the net, but I was strongly  
> hoping there is a much more clever and obvious solution that I was  
> just overlooking ;-)
>
>> Cheers,
>>
>> Luis.
>
> Best
>
> Klaus Major
> klaus at major-k.de
> http://www.major-k.de
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list