I'm interested in this as well. Two points to make. One, why not start with
postgresql, which if I understand correct already supports getting ids in
bulk_create. I think the "how to support getting ids in MySQL" is a
separate issue. Second, I strongly agree with Shai, falling back should
eithe
On Tuesday 29 March 2016 13:19:01 Anssi Kääriäinen wrote:
>
> Personally I think we should just rename the method to fast_create()
> and allow it to fall back to single row at time behavior. This way you
> could safely call it for any objects on any database and know the
> results will be OK. I do
For MySQL InnoDB tables the behavior is described here:
http://dev.mysql.com/doc/refman/5.1/en/innodb-auto-increment-handling.html,
see "Gaps in auto-increment values for “bulk inserts”" item. So, you
are safe as long as the lock mode is correct, and assuming the lock
mode is the default is OK for
Hi,
I worked on supporting bulk_insert for multi table inheritance here [1] I
would like to get some feedback.
bulk_create can be used in one of 2 ways
1) If you already have parent records in the database and want to
bulk_insert into the child table only.
2) There isn't any parent records, and
