On 2 Lut, 10:52, "Leslie P. Polzer" <[email protected]> wrote:
> The cl-prevalence transaction log does not maintain object identity > correctly. > > This misbehaviour will screw up your data relationships when you exit > your Lisp without closing stores (snapshot save/restore works as it > should). > > I already have a working fix for this, but it's nowhere near release > quality > (e.g. no tests, doesn't fix managed prevalence, XML serializer > only, ...). Does it concern the Weblocks cl-prevalence datastore backend only, or cl-prevalence proper, too? I'm concerned because I have recently deployed a non-Weblocks application using cl-prevalence and would like to prevent any problems as early as possible (no problems so far, though, but perhaps that's due to the way I've designed my transactions). Best regards, Daniel Janus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
