on 5/30/01 14:03, Steve Baxter at s.baxter-mail (at) improvision D.OT com wrote:
>> So you want do LONG write into BLOB and in the same time work with other >> records (of other tables), yes? Looks as feature of Server :-) > > Yes that's what I want to do. The blob write might be 100-200MB, doing it > asynchronously will enable the user to continue working while it saves > changes in the background.
another question: this 100-200MB come from other file I think. Not from RAM, yes? If you have so big BLOB for one record then how many records do you have in total ???
> Actually, as long as the database is semaphored, this might work OK. My app > caches quite a lot of the data from the database - in the worst case the > user would have to wait on a database read while the write thread was > completing the current write, but the caches minimise reads in most > circumstances. I can also write the BLOB a bit at a time (say 256K) which > will give blocked threads a chance to access the database quite often.
Yes Steve, I think this is the best way for you now. Save BLOB by parts.
> What would be really cool would be for Valentina to do async writes - then I > can write my BLOB into Valentina's cache and the DB would write out the > cache asynchronously. Might be a little risky though...
-- Best regards, Ruslan Zasukhin
------------------------- Paradigma.
e-mail: ruslan@paradigmasoft.com web : http://www.paradigmasoft.com
To subscribe to the Valentina mail list send a letter to valentina-on (at) lists D.OT macserve.net
------------------------------------------------------------- The Valentina mailing list is brought to you by MacServe.net For info on lists services, see http://www.macserve.net/lists.html ©2001 Ruslan Zasukhin |