Uwe (ObjectBox)

Thanks for reporting! This currently can not be fixed as the ObjectBox Java generator generates Java code and: > Java has no concept of "type aliases" and can't see them...

As the message says, it is not supported to attach to a store that is already opened in the current isolate. The code should either keep a reference to an...

Thanks for asking. This is indeed a little confusing. The `Store.isOpen()` check works on the process level (you can see it calls a C API), so across Dart isolates. The...

Thanks for reporting, I could reproduce this! A workaround for this it to modify the `ToMany` in the `Owner` class to explicitly specify the Backlink source: ```dart @Backlink('owner') final tasks...

Release `5.0.1` is available which resolves this issue. To update to this release, for a Flutter project run `flutter pub upgrade` or for a Dart Native project `dart pub upgrade`.

Thanks for reporting! There is https://docs.objectbox.io/relations#how-toone-works-behind-the-scenes But I agree this can be improved for Dart, including the generator error message. Note for us: internal issue `objectbox-dart#140`

@pwaltron Thanks for your note. The next release will, similar to Java, introduce a `@TargetIdProperty` annotation. It will allow to set a name different from the default name for the...

Release `5.0.1` is available which introduces the mentioned `@TargetIdProperty` annotation and also provides a helpful error message in case a regular property collides with an implicitly generated target ID property...

Thanks for reporting! TL;DR: see #436 for a possible workaround. A little background: the ObjectBox database runs on the process level. Only some state lives in the Dart VM, but...

I've linked the issue with exactly that workaround: > TL;DR: see https://github.com/objectbox/objectbox-dart/issues/436 for a possible workaround. Here is the direct link: https://github.com/objectbox/objectbox-dart/issues/436#issuecomment-1219356368