Uwe (ObjectBox)

@tvvbbb OK, so I understood correctly (for me: see my previous comment). Thanks! -ut

I don't know if there are plans to make the plugin code public, right now it is not available. cc @greenrobot

@HugoGresse The ObjectBox plugin is only used at build time so using it shouldn't cause any issues regarding licensing of your code (but again, depends on your policy of course).

@chakflying > then set all the fields This sounds like the existing `REPLACE` strategy could work for this, no? https://docs.objectbox.io/entity-annotations#unique-constraints

@deliqs What's your use case? E.g. why can't `put` be used in your case?

@deliqs Thanks for the details! Yes, if a replace occurs with `ConflictStrategy.REPLACE` the new inserted object will have a different `@Id`. And relations would still point to the removed objects...

@Schmalztopf No, we will share once a feature is being worked on and when it's done. To help us track interest, thumbs up the first post.

MyObjectBox generation will only work for the module where the ObjectBox plugin is applied and only if the plugin can find `@Entity` classes in that modules sources. So it is...

For now we have no concrete plans for this. Leaving this open as a suggestion. -ut

@shashi-appgolive It should be fine to have entities in different modules, if you also apply the plugin and have a separate database (e.g. supply a different name when building BoxStore)...