Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,172 of 19,505    |
|    Bob Barrows to andrew    |
|    Re: Should I split the record?    |
|    27 Mar 11 21:34:23    |
      From: reb01501@NOSPAMyahoo.com              andrew wrote:       > Hello all,       >       > This is a newbie design question. I have a table with the following       > fields       > TABLE A       > ID, Prop1, Prop2       >       > I expect that I might have multiple concurrent users accessing the       > same record (in a recordset via SELECT). If I expect to have users       > modify either Prop1 or (XOR) Prop2 I should also expect the DB to       > complain since one of the users would have the record locked (I'm       > learning lots about locks). Would that complaint be an ADO exception       > or would the locked out user just wait for the record to be free? Would a       > better design for this scenario be       > TABLE A       > ID, Prop1       >       > TABLE B       > ID, Prop2       >       > this way the users would not interfere?       >       My answer is based on the assumption that Prop1 and Prop2 are "repeating"       attributes, i.e., multiple instances of the same type of property (same       datatype, etc.) If that's not the case, then my answer does not apply.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca