On Dec 14, 11:16 am, Jeremy Evans <[email protected]> wrote:
> ... Also, there may be a reason why a user wants to insert > each row with a separate insert query on MySQL, PostgreSQL, and MSSQL. > Combining the methods would no longer allow that. So I don't see a > benefit to your proposal. > Well, that would still be possible, since that single method would take options, that would specify the behavior desirable (one sql - if possible, or multiple insert statements). There are just too many similarities between multi_insert and insert_multiple to warrant 2 separate methods. But I do understand your point about backwards compatibility, killing those 2 methods or one of them would be a good change only for the 'major' release, that is allowed some non-backward compatible changes. Backwards compatibility is good, but taking it to the extreme (NEVER break it) stifles software. > > Again, current API is functional, it is just a bit vague because of a > > 'mushy' contract of multi_insert method. > > Welcome to the world where not all databases support exactly the same > set > of features. :) I understand, it is a daunting task to try to map all those seemingly incoherent dialects of SQL to one API. And batch data loading is exactly the area where databases differ the most. :) -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
