I've just spent 15 minutes staring at weird sldb traces until I realized that the only way for them to happen is if something got seriously corrupted.
Am I correct in understanding that the current weblocks with clsql store will crash and burn because it isn't threadsafe? (all it took in my case was one googlebot and me clicking in the app) Since I'm lazy, I figured I'd check here for quick advice -- if I pull this: https://www.bitbucket.org/S11001001/weblocks-clsql-fluid/changeset/e453eb9183bf/ will I be fine? Or is there more to it? --J. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
