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...
- james On 7/17/06, zdennis <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rick Bradley wrote: > * zdennis ([EMAIL PROTECTED]) [060716 20:33]: > > Not commenting on the viability of the patch as a whole, but perhaps > rather than :fast / :fastest it would be better to drop :fast (which as > I understand it simply reduces the number of inserts required, behind > the scenes, without otherwise changing the create() behavior(?)) in > favor of a speedy default, and renaming :fastest (after all, what's > "fastest" now may well not be in the future) to be indicative of > function -- i.e., that it doesn't create the AR objects being created in > the database. > What about :optimize=>'norecords' or :return=>'norecords' ? The later would get rid of optimize key but it probably be a better indicate of what is going on? Zach -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEuwePMyx0fW1d8G0RAtFSAKCCgCm7GggPzV6wZCZTHDHtiH7ZFQCbB4ud +yRCgBJWEb5dWjseA0xOrE8= =Y2Mg -----END PGP SIGNATURE----- _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
-- * J * ~ _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
