Hans Kristian Rosbach

In my case, I have a constant influx of new data and a need for periodically bulk shedding old data. So I would love to see support for some kind...

@mtuncer True, that would work for one of my tables. The others have rows that need to stay until they are no longer referenced from the first table. I guess...

Should __arm64__ be added to feature checks around the code as well perhaps?

I agree that this should probably be in a separate CI workflow. Could you fix that @PiotrSikora or do you need any assistance?

@nmoinvaz I did, but I have a different possible solution that I want to present. Just have to get the time to gather and present all the relevant details 😉

@sfc-gh-sgiesecke Stable release, as in 2.0.7 is on my TODO list. I am unable to promise any dates, as there is quite a bit of commits to go through to...

I am also thinking this is not a real issue, but is there a way we can make that clear to Coverity (and other static checkers) in a good way?...

Just ignoring these kinds of warnings will only end up with us answering questions about them time and again, just like zlib does.

Hmm, seems my reply was lost. Adding coverity to the ifdef check did not improve anything unfortunately. Not sure how to make this more clear to static checkers

The scenario @joshtriplett describes is a quite common (and very annoying one) when building packages, and I can absolutely see myself hitting that one. Lets say you want to build...