On 06/28/2011 02:43 AM, Victor Hooi wrote:
Shawn,
Thanks for the quick reply =).
If we go with the third approach, what advantages are there to
persisting the models in MongoDB (or something similar like Redid.or
Cassandra), as opposed to a traditional RDBMS? (I just want to get a
good
Shawn,
Thanks for the quick reply =).
If we go with the third approach, what advantages are there to persisting
the models in MongoDB (or something similar like Redid.or Cassandra), as
opposed to a traditional RDBMS? (I just want to get a good handle on the
issues).
Furthermore, is there a
Shawn,
Thanks for the quick reply =).
If we go with the third approach, what advantages are there to persisting
the models in MongoDB (or something similar like Redid.or Cassandra), as
opposed to a traditional RDBMS? (I just want to get a good handle on the
issues).
Furthermore, is there a
If you're using Django 1.2 or higher you can take advantage of the
multi-database support by adding the 'using' kwarg to your model.save().
This will allow you to ensure that the model saves successfully (is
valid) in the 'holding' database, and move it to your 'live' database later.
You
heya,
We have a CSV file that we are importing into a Django application, and then
creating the appropriate models and relationships.
At the first page, we have a file upload form where the user selects a file.
We then parse the file, and return a second page showing them what would be
5 matches
Mail list logo
