why import do not return imported ids, when it called in sidekiq worker ?

[Asdfif]

I use activerecord-import in Sidekiq worker and if I call worker by .perform_async then I get this result:
#<struct ActiveRecord::Import::Result failed_instances=[], num_inserts=1, ids=[], results=[]>

but if I call worker by .new.perform then I get this result:
#<struct ActiveRecord::Import::Result failed_instances=[], num_inserts=3, ids=[375, 376, 377], results=[]>

why?

[jkowens]

If you can share the sql that is being executed in each scenario we may be able to help. Right now there isn't enough information. Is it the same model/table that you are importing into? You must be using Postgres?

[darnat]

Actually facing a very similar issue. I have an import running in Sidekiq and no ids are being returned. This case scenarios is covered by specs, and the specs are passing (it does return ids). It just doesn't work when running in production/sidekiq.

[Asdfif]

@jkowens I use MySQL.

sql query with sidekiq worker perform_async:

result = ModelName.import array, validate: false
D, [2023-03-03T10:17:51.725232 #64421] DEBUG -- :   ModelName Create Many (120.5ms)  INSERT INTO `table_name` (`id`,`prefix`,....) VALUES (NULL,'test_bulk11@test.com',.....),(NULL,'test_bulk21@test.com',....),(NULL,'test_bulk31@test.com',...)
#<struct ActiveRecord::Import::Result failed_instances=[], num_inserts=1, ids=[], results=[]>

sql with sidekiq worker new.perform:

result = ModelName.import array, validate: false
   (0.6ms)  BEGIN
   (2.1ms)  INSERT INTO `table_name` (`id`,`prefix`,...) VALUES (NULL,'test_bulk11@test.com',...)
   (1.3ms)  INSERT INTO `table_name` (`id`,`prefix`,....) VALUES (NULL,'test_bulk21@test.com',)
   (3.2ms)  INSERT INTO `table_name` (`id`,`prefix`,....) VALUES (NULL,'test_bulk31@test.com',....)
   (2.0ms)  COMMIT
#<struct ActiveRecord::Import::Result failed_instances=[], num_inserts=3, ids=[412, 413, 414], results=[]>

[jkowens]

@Asdfif Returning ids is not supported for MySQL. Unlike Postgres, MySQL does not provide a way to return the ids of inserted rows.

The example you show with the imported ids being populated doesn't seem right. Why did it produce 3 insert queries?

[Asdfif]

The example you show with the imported ids being populated doesn't seem right. Why did it produce 3 insert queries?

@jkowens I did not understand yet why there are 3 queries. trying to figure it out

[Asdfif]

Returning ids is not supported for MySQL. Unlike Postgres, MySQL does not provide a way to return the ids of inserted rows.

If MySQL does not provide a way to return the ids of inserted why it returns ids when i use new.perform...