objectbox / objectbox/objectbox-dart
Multiple Store, generates all tables for each Store
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 1.2k
- Forks
- 162
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
In my application, I want to have multiple Stores (separated by features) and each one with its own objects (they don't share objects). I've already created several Stores... everything's fine, but when viewing the MDBs through the desktop viewer (via Docker), I've seen that each MDB generates all the tables for all the objects (even though I only use some objects in some Stores and others in others).
Can I specify which Store classes belong to the Store so that it only generates the specific tables?
Sorry for my English.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the multiple Store setup and the Store classes described in the issue, then verify the behavior using the MDBs in the Docker-based desktop viewer. Done would require a documented or implemented way to associate selected Store classes with each Store so its MDB contains only the intended tables, with the resulting behavior confirmed in the viewer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100