Skip to content

Conversation

@Yevhenii-Kushvid
Copy link

@Yevhenii-Kushvid Yevhenii-Kushvid commented Nov 17, 2024

In recent project I faced the issue of performance, and found in AriTable api bulk operation: here is my proposal implementation of them for airrecord gem.

  • Table#bulk_create
  • Table#bulk_update
  • Table#bulk_delete

and additional helper for record finding

  • Table#find_or_create
  • Table#count

link to API documentation

@Yevhenii-Kushvid Yevhenii-Kushvid changed the title add bulk operations: create, update, delete; and find_or_create method add bulk operations: create, update, delete; and find_or_create method for single records Nov 17, 2024
@Yevhenii-Kushvid Yevhenii-Kushvid changed the title add bulk operations: create, update, delete; and find_or_create method for single records add bulk operations: create, update, delete; and find_or_create + count methods for single records Nov 17, 2024
@AdrienGiboire
Copy link

Thanks for your work. I don't know if this gem is still watched/maintained. It looks like it's not. Anyway, if I manage to make it work on my project, I'll definitely integrate your work too!

@Meekohi
Copy link
Collaborator

Meekohi commented Mar 27, 2025

It's come up a couple times already:
#84
#91

I'm not strictly opposed to adding batch operations, but it needs testing and documentation, (would also be nice to have some information on how much performance you gain with this approach so people know when it makes sense to use it).

@AdrienGiboire
Copy link

AdrienGiboire commented Mar 28, 2025

Both mentioned PR came with tests. The first one was left unaddressed for months. The second one was closed due to increased complexity.

Also, I don't get this point:

would also be nice to have some information on how much performance you gain with this approach so people know when it makes sense to use it

Airtable API offers bulk operations. Why not support it in Airrecord?

Regarding performances and when to use it, that sounds like an Airtable concern, not an Airrecord. Plus, how come one would have to justify how running multiple requests is worst than running a bigger one?

What am I missing?

@Meekohi
Copy link
Collaborator

Meekohi commented Mar 29, 2025

I don't think you're missing anything -- some combination of those two PRs that includes tests and documentation would probably be pretty good! Neither PR on its own was ready to merge, nor is this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants