Reactive dict/map between documents

[mitar]

It seems a common data structure one would like is the following:

{
  related: {
    <id of a document>: {
      subfield: "Subfield value"
    },
    <id of a document>: {
      ...
    }
  }
}

So a dict/map where keys are IDs and values are a subdocument with few fields of a referenced document. One can do that as a list for now, but I think having a dict/map would be beneficial for easy direct access if key (document id) is known. But current code does not yet support keeping subdocuments in sync for such structure.

[mitar]

This is useful when there is no need for an order of those related documents. If order is needed/important, then list is required.

[mitar]

In fact, I still managed to define things with whatever is currently available, so the good question is how much this is really needed. :-)

[moonrockfamily]

I'm interested in your use case for identified related documents with a subset of fields kept sync'd. Can you share your example/general case. Much appreciated.

[mitar]

I do not understand your question. This ticket is about one particular structure of data and not a general ticket for questions about PeerDB.

[moonrockfamily]

It seems I misunderstood your idea/proposal. I initially thought you were proposing an alternative/extension to the existing ReferenceField capability fieldName: @ReferenceField and was seeking to understand your use case/why it wasn't sufficient... as per README:

class Post extends Document
  # Other fields:
  #   body

  @Meta
    name: 'Post'
    fields: =>
      # We can reference other document
      author: @ReferenceField Person, ['username', 'displayName']
      # Or an array of documents
      subscribers: [@ReferenceField Person]
      reviewers: [@ReferenceField Person, ['username', 'displayName']]

[mitar]

Yes. Here is a ticket for a different structure than what is currently implemented. But I have not seen really a need for it. I prefer to use list of subdocuments anyway. Also, I do not like data schemas where keys have meaning. So ticket/idea is here, but this is it.

[mitar]

This can also work only if <id of a document> does not contain a dot (MongoDB restriction).