From: Paul V. <pa...@vi...> - 2006-05-28 00:32:46
|
Hi all, First, thanks for your input everybody. In addition to what I said earlier, I've added UIB to the component sets and mentioned JVCL too. I've also added a short section on IBPP (further down, in the API section). Ernesto: > in the doc, you go on saying that 'Firebird allows any row to be > visible to any transaction, even if other transactions have updates > pending for it.' I know that you are talking of the non-blocking > nature of MGA, but it also can be interpreted to seem that you can > do dirty reads. Maybe it's my (poor) English... No, you're right: the text (it's not mine, btw!) doesn't actively suggest that dirty reads are possible, but it also doesn't exclude the possibility. I've added one fairly general sentence now, stating that different transactions may see different versions of a row, but I don't want to go into details here about dirty reads or isolation levels. There's an entire chapter on transactions in UFB. > Finally, there is another client option for Firebird: the .Net > driver, (...) I think with this driver you don't even need to > install the fbclient.dll as it has implemented all communication > protocol in c#, but i may be wrong here No, you're right again :-) I've added this info too. Pavel: > I don't mean they [Services API and Manager] are synonymous, I mean > they relate each other closely, and that fact should be in minds of > (new) developers, not to be confused later. Understood - it's been taken care of now. > I mean, that there exist problems accessing FB via BDE; and > developers should know that most probably no one will fix the > problems in the future. ...and they will probably get worse. Okay, I've added Yet Another Warning to the client/server chapter. I wil probably build and upload a fresh PDF within a couple of days. Greetings, Paul Vinkenoog |