News for hackers. Stuff that matters.
Re:Django 1.4 final released by ubernostrum on Friday March 23, 2012 @02:37PM (#3746507)
This is the correct behavior, really. Bulk insert is not for cases where you have complex per-record validation or processing logic that also needs to be run in the application layer. It's for "I have all this data ready to go, now just shove it in there as efficiently as possible". If you need to have validation and additional per-record processing, signals, etc., insert the objects through the ORM normally. Yes, it'll be slower, but that's the price you pay for doing per-record processing.
Re:Django 1.4 final released by notyourwork on Saturday March 24, 2012 @11:18AM (#3749556)
To add to this, you could write your own validation method for a model and have your model's save method call this.

When processing bulk data sets you can iterate over calling your own validation then perform bulk insert knowing its validating. And your save will still validate as before.