Look for the post_save signal. Once you can attach your own function to that signal (make it listen for the signal and kick something off), you can probably have Django dump the raw SQL query that is created to a text file. I don't know the syntax for that, but check the django.db docs.
Having said that, this seems like a really hacky workaround. I'd see if there's some "best practices" method of having distributed databases that can sync. I'm guessing it's not going to work with sqlite3, though. If it's a Django site, why aren't you hitting the same database from work that you are from home, anyway? I'd think you'd be using the same URL. The only exception is if you're doing some development at home in a test bed, but then the data you create wouldn't be "real" and shouldn't go into the production database. Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
