> Does this require BDB 4.7? As I recall, conflict detection used to > require a separate process to run correctly but there was a change in > 4.6 or 4.7 to allow you to do this in the same process.
The function in question is DB_ENV->set_lk_detect, which is available at least since 4.5 (just verified). I have only tested this with 4.7 though, so we might want to put the patch on hold until then. > I can dig back into this to refresh my memory unless you are confident > you're up to speed. No, that's fine. Everything you wrote makes sense. I'm going to test the other BDB versions and probably give Allegro a go to check on cooperative mt. It might also make sense to offer the external db_deadlock solution as an option. Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/ _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
