Zeoslib Portal

I'm stumped so far. Using a branch at: add ORA_01089_immediate_shutdown_or_close_in_progress as provided by aehimself, Which should be before any of my changes. I get: Connected Memory Used : 782 KB (801084 bytes) Memory Reserved: 2.49 MB (2621408 bytes) Query.Open: CachedLobs: False in 8731ms Memor...

I'm working on this. I'll report back when I learn something. Btw an easy way to test is just to use something like:
-Mark

Can you put some breakpoints in and make absolutely sure that LobCacheMode isn't being set to OnLoad anywhere? That much extra memory use can only mean that the streams are being cached, right? I'm testing with all three LobCacheMode values and things seem to work the way I'd expect as far as when t...

Can you try the new version that has my full LobCacheMode conversion? It's possible it's something I introduced in the test code and then fixed in the final version. I don't see any issues with memory consumption here even when looping through thousands of pretty big clobs (with LobCacheMode set to ...

I can't seem to cause the problem here (though granted I'm running with the "final" version of LobCacheMode instead of the test version.) I open an uncached dataset with lots of clobs, move up and down many times and I don't see memory increase at all. Any tips on causing it? Any settings ...

It's definitely not on by default so that's probably not it. Can you run your test before my commits related to LobCacheMode? If you aren't changing the value it shouldn't be affecting this, but I'd love confirmation. I use FastMM for leak detection and I haven't seen any lob related leak reports, b...

Are you using TryKeepDataOnDisconnect? That will switch CachedLobs on. Just a thought! Your assumption about CachedLobs = false is correct btw, it should just read the stream and then release it after. I'll test here using LobCachedMode and see if I see a problem.

-Mark

Thanks! I've issued a new pull request with the test suite changes. I changed the test name to be more accurate, I assume they're read using rtti? I couldn't find a reference to the test name anywhere else in the code and the test compiled ok, but I need to look into how to setup the config file for...

I've put in the pull request. A few notes: I removed the code related to CachedLobs in procedure TZCachedResultSet.ResetCursor as I thought it might cause an issue for drivers that hard code the value. I put the enumeration and some helper code in ZDbcIntfs. There may be a better place for it. The L...

I think, when setting TryKeepDataOnDisconnect, the lobCacheMode should be set to always fetch and cache LOB contents. I think this is what Egonhugeist wanted to do with the line you mentioned. My personal need for this is TryKeepDataOnDisconnect = True combined with lcmOnAccess. This is mostly due ...

Hi Jan,

Sorry for that! I'll use one of those methods for future stuff.

-Mark

The SetDateFormat and SetTimeFormat procedures use FFormat instead of either FDateFormat or FTimeFormat. Here are the fixed versions: procedure TZAbstractTimestampFormatSettings.SetDateFormat(const Value: String); begin if ((FDateFormat = nil) and (Value <> '')) or ((FDateFormat <> nil) and (Value =...

Found it! It turned out not to a problem with the code I put in the previous post, but had to do with using TryKeepDataOnDisconnect combined with testing lcmOnAccess. Setting TryKeepDataOnDisconnect set FCachedLobs to true, which then causes problems with lcmOnAccess. Once we replace the existing Ca...

Back to the drawing board! Don't bother testing this for a bit, it's not working at all correctly. I was testing with randomly generated clob text and didn't notice that the cached clobs are not showing up on the correct record. Changing the CLOBs to a sequential number shows the problem. This expla...

[Update - Ignore this - fixed it] If people could test or just look at what I've done and see if they can see anything wrong I'd appreciate it. In my testing with lcmOnAccess I will occasionally get the error: raised exception class EZSQLException with message 'SQL Error: OCI_INVALID_HANDLE Code: -2...