Warning: This python script is designed for Django 0.96.
It exports data from models quite like the `dumpdata` command, and throws the
data to the standard output.
It fixes glitches with unicode/ascii characters. It looked like the 0.96
handles very badly unicode characters, unless you specify an argument that is
not available via the command line. The simple usage is:
$ python export_models.py -a <application1> [application2, application3...]
As a plus, it allows you to export only one or several models inside your
application, and not all of them:
$ python export_models.py application1.MyModelStuff application1.MyOtherModel
Of course, you can specify the output format (serializer) with the -f
(--format) option.
$ python export_models.py --format=xml application1.MyModel
- tool
- dump
- serialization
- export
- db
- database
This is nothing fancy and hasn't much to do with django itself, I just searched for this information for quite a while and thought it may be useful for others.
If you use IE7 (and maybe IE6), it will block cookies in iframes, if the iframes content comes from another server (quite common, I think).
The P3P specification lets you declare your privacy settings in a format interpretable by browsers, essentially you can tell IE that you adhere to "don't be evil", and are allowed to handle cookies afterwards.
I don't think that makes much sense, but it seems that it is the only way to make IE accept cookies in iframes.
I had no idea that django made it that incredibly easy to "patch" the response-header, but it does! :)
- p3p
- ie7
- internet
- explorer
- iframe
- privacy