Simon Eskildsen

That's cool. Someone who stumbled upon this ticket should consider implementing that. But I'd suggest going a bit back and forth here on a good API first!

Also just saw that Airtable has a metadata API now. That could be really cool to work on Airrecord integration for. Opens up a lot of possibilities where it's harder...

That seems sensible to me. Not crazy about the name, but I think this is the simplest.

Nah. Let's not sweat it. The functionality would be the same. Introducing relations is not worth it. This maps to the Airtable naming, so let's do what you suggested :)...

Maybe one thing I'd suggest is to just call it `update`, and then also have a `update_or_create`, as well as a `create` which can also take an enum.

Please consider submitting a patch

It's too bad you can't finish it, is it because you ended up not needing it in your own project?

Those should be pretty easy to fix. Happy to accept a PR and make it into a patch release :)

Good with me :)

I'm happy to go the AR-route. I'm wondering if we can lean on some of the AR-tooling, instead of re-inventing it from the ground up? I'm not super familiar with...