multiuser application(please help)
Samir Badaoui asked how to manage multiuser access from a Visual Basic client to Informix 7.30, as the developers proposed extra serial number and timestamp columns on every table. Obnoxio The Clown, Andrew Hamm and sudhakar all advised using the database's own record locking instead of hand-made optimistic schemes, since the DBMS handles concurrency. Answered, in a robust tone.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
sory for my html version, this is text version of my question my question is about data integrity in the client/serveur environnement. My client is a visual basic application and my serveur is nformix 7.30. What is the best way to manage multiuser application. Actually the company who want to develope the visual basic application propose to add 2 fields in every table, a serial number to identify the row and a time stamp to identify the last time the record was created or updated. but I don't think that is a good idea. please have you any proposition for a best way to manage multiuser activity in this case ??? thanks for any suggestion _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
In the year of Our Lord Sat, 10 Feb 2001 21:54:44, "samir BADAOUI" <samir_badaoui@hotmail.com> spake, saying: >sory for my html version, this is text version of my question > >my question is about data integrity in the client/serveur environnement. My >client is a visual basic application and my serveur is nformix 7.30. > >What is the best way to manage multiuser application. Actually the company >who want to develope the visual basic application propose to add 2 fields in >every table, a serial number to identify the row and a time stamp to >identify the last time the record was created or updated. but I don't think >that is a good idea. > >please have you any proposition for a best way to manage multiuser activity >in this case ??? F********************************************************!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Fire your application developers immediately. Use record locking to manage multiuser activity.
Obnoxio The Clown wrote in message <3a87cbc0.7993764@130.133.1.4>... >In the year of Our Lord Sat, 10 Feb 2001 21:54:44, "samir BADAOUI" ><samir_badaoui@hotmail.com> spake, saying: > >>please have you any proposition for a best way to manage multiuser activity >>in this case ??? > >F********************************************************!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!! > >Fire your application developers immediately. > >Use record locking to manage multiuser activity. Ahhh - you understood the question! Is THAT what he means? Optimistic locking? How sweet! Yeah - what the clown says - forget it. Since you told me privately that you understand informix already, you know how to program it. Forget about wasting time with hand-made multi-user programming. If you want to do that you may as well use flat files and forget about using an intelligent database engine. Propose that to the other engineers.
hey, dont confuse with developin application for concurreny and all that stuff, bcos dbms take care all of that .. i guess informix is not that bad... sue your developer.. bye sudhakar -- Posted via CNET Help.com http://www.help.com/