Skip to main content
Drupal Answers

Return to Question

added 2 characters in body
Source Link
maartend
maartend
  • 121
  • 1
  • 8

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, could Iit should reduce the scope of your query? Is there a possibility to do that with the current version of the module, or am I just not getting it?

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, could I reduce the scope of your query? Is there a possibility to do that with the current version of the module, or am I just not getting it?

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, it should reduce the scope of your query? Is there a possibility to do that with the current version of the module, or am I just not getting it?

deleted 9 characters in body; edited title
Source Link
avpaderno ♦
avpaderno ♦
  • 97.9k
  • 15
  • 164
  • 284

Mongodb module fields: Collection per content type

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, you could I reduce the scope of your query no ? Is there a possibility to do that with the current version of the module?

Or, or am I just not getting it?

Mongodb module fields: Collection per content type

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, you could reduce the scope of your query no ? Is there a possibility to do that with the current version of the module?

Or am I just not getting it?

Collection per content type

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, could I reduce the scope of your query? Is there a possibility to do that with the current version of the module, or am I just not getting it?

Source Link
maartend
maartend
  • 121
  • 1
  • 8

Mongodb module fields: Collection per content type

I just started experimenting with the mongodb module and its fields storage module on a clean drupal install and it all seems to work fine. But what I noticed is that the content of the 2 custom content types is stored in the same collections (fields_current.node and fields_revision.node).

Wouldn't it make sense to have a separate collection for each content type? As queries are often per content type, you could reduce the scope of your query no ? Is there a possibility to do that with the current version of the module?

Or am I just not getting it?