Skip to content

Query error for property with large String #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gurunbg opened this issue Mar 3, 2020 · 6 comments
Closed

Query error for property with large String #94

gurunbg opened this issue Mar 3, 2020 · 6 comments
Assignees
Labels
bug Something isn't working help wanted Looking for contributors (ideas, comments, code, etc)

Comments

@gurunbg
Copy link

gurunbg commented Mar 3, 2020

I saved large string in database but when try to make query to get it I get error:

E/flutter (31707): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: Exception: ObjectBoxException: find: 10098 Do not use vector-based find on 32 bit systems with big objects
E/flutter (31707): #0      checkObxPtr (package:objectbox/src/bindings/helpers.dart:15:5)
E/flutter (31707): #1      Query.find.<anonymous closure> (package:objectbox/src/query/query.dart:574:26)
E/flutter (31707): #2      Store.runInTransaction (package:objectbox/src/store.dart:69:16)
E/flutter (31707): #3      Query.find (package:objectbox/src/query/query.dart:573:19)

This problem is only for x86 Android Emulator and it is ok for physical devices.
I founded very similar issue for Java Objectbox that was fixed 1 year ago - java issue

Thanks!

@vaind
Copy link
Contributor

vaind commented Mar 3, 2020

Yes, 32-bit support for large objects requires some special handling, calling visitor-based objectbox-c APIs instead of array-based ones and that's currently not implemented in the objectbox-dart lib code.

If anyone was interested to pick this up, I can help with more details/guidance and there's also objectbox-go which can be relied upon as the logic source, e.g. in box.go

As a workaround for the time being, you can use the x64 emulator.

@vaind vaind added bug Something isn't working help wanted Looking for contributors (ideas, comments, code, etc) labels Mar 3, 2020
@vaind vaind self-assigned this Mar 3, 2020
@vaind vaind mentioned this issue Mar 4, 2020
@vaind
Copy link
Contributor

vaind commented Mar 9, 2020

Fixed in v0.6.2

@vaind vaind closed this as completed Mar 9, 2020
greenrobot-team added a commit that referenced this issue Feb 12, 2024
Add a new condition class for each one, with methods explicitly named to
ensure it is clear how values are passed to the database. This does not
break existing user code as both condition classes inherit from the
previously used QueryIntegerProperty class.
greenrobot-team added a commit that referenced this issue Feb 12, 2024
Hide the implementation detail of converting to milli/nanoseconds,
leave it to the docs. Most users should be aware that time-zone info is
not stored and how to use DateTime with UTC time in Dart.
greenrobot-team added a commit that referenced this issue Feb 12, 2024
Date conditions: fix oneOf/notOneOf, increase test coverage #94

See merge request objectbox/objectbox-dart!71
@mirkancal
Copy link

I'm getting same error with langchain and openai embeddings

StorageException (StorageException: Do not use vector-based find on 32 bit systems with big objects (OBX_ERROR code 10098))

@greenrobot-team
Copy link
Member

@mirkancal As the error message indicates, the vector functionality is currently only supported for 64-bit platforms. If you are running on a 64-bit platform, please open a new issue with more details, notably about the platform you are running your code on!

Side note: Flutter only supports 64-bit platforms now (with the exception of some older 32-bit ARM Android versions).

@mirkancal
Copy link

@greenrobot-team thank you, let me check if I set it to 32-bit somehow. I'm not sure how I can choose 32 bit iphone 16 pro emulator with ios 18.

@greenrobot
Copy link
Member

I think the error message might be misleading in this case. Can you open a new issue with a full stack trace please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Looking for contributors (ideas, comments, code, etc)
Projects
None yet
Development

No branches or pull requests

5 participants