Locking problem

Thread View: borland.public.cppbuilder.database.multi-tier

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Indra Gunawan Thu, 26 Jul 2001 08:46

#556

Author: Indra Gunawan
Date: Thu, 26 Jul 2001 08:46

14 lines
1512 bytes

I am using a database server that cannot perform locking. And my database
program will be run so that in the server there will be many instances of
the program, just like opening five or more notepad on your desktop.

Nah, the problem I am facing is how can one instance know that another
instance is performing modification so, it can wait for a while until the
previous task finish. Can I create a shared memory so those instances can
know each other's existence and furthermore know what records that is valid
or not for modification and avoiding collision problems.

Thanks for your assistance

Best Regards,
Indra Gunawan

Re: Locking problem

#561

Author: Tharun Pillay
Date: Wed, 01 Aug 2001 21:50

7 lines
1090 bytes

My idea would be use sockets. If theres a server, and there's a client, then
make 'em talk - you'll be able to let them know who's doing what, when.

Otherwise write a COM server and client.

Regards,
Tharun

Re: Locking problem

#481

Author: Jayme Jeffman Filho
Date: Fri, 17 Aug 2001 17:02

7 lines
1011 bytes

You can create a table where you insert a record which points to the table
and data that is being updated and delete the record after the update
operation is finished.

I hope it helps.

Jayme.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads