Create on model collections does not assign database generated Ids about fluent-kit HOT 4 CLOSED

This is a known limitation of using the collection version of create() (whose only benefit over doing it one model at a time is that fewer INSERT queries are issued). Unfortunately, this logic was originally designed around the incredibly foolish (to put it politely!) decision to make UUID the default ID type for models (thanks to Mongo), where the ID is generated by Fluent rather than the database.

Even more unfortunately, though, I can't honestly say I have any plans to fix this at this point; this is a very long-standing behavior (no matter how poorly chosen it may have been...), and development effort on Fluent is now directed towards Fluent 5. That being said, if someone were to open a working PR to fix the problem, I'd be inclined to accept it!

from fluent-kit.

I can safely say with certainty that Fluent 5 will not have this issue (or a myriad of others stemming from similar design flaws) 🙂.

from fluent-kit.

I may be completely wrong about my assumptions here, I'd appreciate any pointers on getting this moving in the right direction. Thank you.

from fluent-kit.

@gwynne as always, thank you for addressing my concerns so quickly.

Would it be possible to consider addressing this limitation in Fluent 5? I'm open to working around this for the time being in my code, by using single inserts.

from fluent-kit.