Open mapkyca opened 5 years ago
Storing annotations on the actual object...
I'm encountering this very issue while trying to fetch individual reply annotations, the whole object is returned...
While we are refactoring relations between tables, I would also make annotations have a relation to their (remote) user entity.
This will ensure remote user info such as owner_name
& owner_image
are always current, for example.
While trying to do this:
List, edit, delete or otherwise manage annotations and comments
I encountered this error:
It's not really possible, as annotations are stored directly on the object
Some other notes:
The current data model is very heavily influenced by the fact it was originally stored in mongo only. Storing annotations on the actual object is utterly crazy when you're in a relational world.
Redesign the data model to store annotations in its own table.
Give us some context:
version.known
file