Hi, The real problem is not in a place where h2 client stores temp blobs but in the fact that it stores blobs to temp files at all. I think it should not do this. It seems that it does this on each row fetch but this is incorect since even if you have selected some result set conatining blobs you are not necessarily will access this blobs but they are all downloaded to the client machine. This can be ok if your network is fast enough, blobs are not so big and you do not fetch too many rows but if this is not the case you will have performance problems. Also the write access problems you mention. So the right way to fix this all is to get rid of temp blob files on client so that result set will contain only some kind of links to remote blobs instead of whole blob data.
regards, S.Vladykin -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
