I may be a little out of date now... but I had this problem with
3.23.18... you need to supply the PATH to the Berkeley DB libs on the
configure command line too. I can't remember the name of the cmdline
param though. I seem to remember this being a bit obscure too, but it
makes perfect sense when you think about it!
Does that mean that 3.22 doesn't have support for Berkeley DB?
If so, is it worth the risks to run a beta SQL server, just for the
transaction log?
This sql server will be responsible for mission critical data and I really
can't afford to have code that will cause problems, but the transaction
logging feature will help us know what has been queried and so on.
Any feedback will really help.
Thanks
-Andrew