one of the things i HATE about mysql, is the 5.0 branch , nothing failed. they specifically wanted everything to go though, and valued that behavior over integrity.
in terms of what happens when something does fail now? I'm pretty sure the mysql and postgres docs have workarounds/solutions for that. i've never had to code for that , as i've only dealt with data dumps. i meant to add in my original post- you can use a log rotation system to just change the 'write to' file every set interval, and then work off that. i think there is a python class that handles that automagically. i didn't think of the threads issues myself. locking would need to be done as mentioned above. two things i'd bring up: - doing something similar in mod_perl, i've had the logging done in a 'cleanup' handler that runs after the connection closes. this can often free up some blocking issues. - IIRC, a friend tried something similar where his apps were posting the data to an central twisted daemon on his lan. that daemon then handled all of the logging , rotating, and misc management. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
