On 7/17/06, James Adam <[EMAIL PROTECTED]> wrote:
Since the behaviour is different from that of create (i.e. no object instances are returned), why not just define a new method which clearly indicates it's aptitude for inserting large amounts of data? Model.import(hashes) or something...
The behaviour is *significantly* different from create as no validations are performed. I'd second the opinion that this isn't really a 'create' scenario, it's much more of an import. I'm still not convinced that a workaround like this is the right way to solve these 'bulk load' / ETL scenarios. Why not use your database's import tools or some really lightweight SQL wrappers? -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
