Flaherty: And then I guess there is a related question following about CLOBs and BLOBs?
Dastur: If it's a character LOB, yes, then it probably makes more sense, if it's like an image I don’t know how we use it with edit and image, but yeah if it's a character large objects, yeah you should be able to modify them.
Flaherty: One more question now, can you restrict which columns can be modified?
Dastur: Yes, absolutely so notice when Robert gets his quotes, he can change certain statuses. You can restrict what column gets modified, even certain ranges. Then Robert logs in, and he can change the status or the remarks column. Only the manager can change that, but you can change the discount. Even when he changes the discount, maybe he gives more than a 100% discount, the validation catches that. You can also have only certain date ranges be permissible.
Flaherty: Okay one more at this point, what if two people are in at the same time, how do you control cross interaction?
Dastur: Well at the back end is the data base so I guess you know whoever writes the data base initially. That is a good question. If you want to make things more secure and more synchronized, you can. You can leverage the database’s own controls and make sure no two people change things at the same time.
Flaherty: Okay, if two people come in at the same time, that is what keeps them from conflicting. What happens if a referential integrity on a database is broken?
Dastur: Referential integrity of the database is typically handled by the database.