🔒 Closed Tulong lang please ang hirap eh..

Status
Not open for further replies.
pero ang better architecture would be gumawa ka ng web service (see about rest api). si api na bahalang magread and write kay db, while sa kanya kokonek sila client.
 
read about THREADS (and or RUNNABLE)...kung sa Java.
- Pero parehong concept din sa ibang programming language.

I think ang hinahanap mo ay what if there are 2 or more users that want to edit a database at the same time.
Or worst, what if there are 2 or more users that want to edit a particular record on the database table all at the same time.
- or in short "COLLISION"

Maraming approach dyan sa case na yan. One solution would be to FLAG or LOCK the data pag user1 ang nauna para walang makaka edit sa data na yan na iba. Or puwede naman, programmatically, compare timestamp of the data time, at kung sino yung latest time, yon ang masusunod.

Goodluck
 
Status
Not open for further replies.

About this Thread

  • 8
    Replies
  • 638
    Views
  • 5
    Participants
Last reply from:
fazz12

Trending Topics

Online now

Members online
677
Guests online
3,374
Total visitors
4,051

Forum statistics

Threads
2,304,615
Posts
29,160,926
Members
1,196,886
Latest member
rumaragasanghotdawgz
Back
Top