> If you don't want to go down that path, we do have built in support
> for JSON, XML, and YAML; so you will need to get your CSV data into
> one of these formats.
I've been using YAML for this purpose before, when using Symfony, and it's a
quite natural way to describe data, only tied by indentation, which should be
a familiar tie for any pythoner.
My question about all of this is regarding the format of the actual file. For
example, in Symfony, you used:
environment:
table:
field: value
field2: value2
You get the deal. Only the fields described are filled. The rest, if non-null,
are filled with either default values or null.
The environment is a neat thing I've been missing in Django so far. Depending
on the way you call your app, you get a different set of settings loaded.
Neat for development/production/staging/else.
Is there some sort of structure, enforced in order to make the file
django-readable? I'd be writing them by hand to make up testing data.
Also, is the fixtures system capable of being used as data-transfer system?
For example, after developing, "uploading" my data to the server. It's just
my opinion, but I find it easier to execute loaddata from my project, than
remembering all the database access data and executing some sort of
administration script inside it to load some SQL I might have dumped from my
dev database.
Greetz,
Chris Hoeppner
www.pixware.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
