If this is a pattern that’s important for you (insert several structs but in one database call) then perhaps worth investing in a helper function that converts to maps and adds the time stamps so you can use insert_all/2? Another approach might be to modify the database schema to have a default timestamp so you don’t have to think about it.

to insert multiple entries in one go

insert_all has been done for this. I would rather write a function to transform data into something suitable for insert_all, as mentionned by @kip, this can be done in one pass, with stream if working on large collection.

It might not change a lot for small dataset, but when You run batches of 10k elements, it’s better to use one insert_all, than 10k independant inserts.

*_all functions are all intentionally lower level apis. They all resolve to a single sql statement. With structs (and even more so with changesets) you can however call insert in ways you need multiple insert sql statements. These requirements are at odds with each other.