Select from collection a on clause from JOIN on collection b










1















I have two collections: games and questions

game schema:



 
_id: ObjectId,
status: 'played',
questions:
[
questionId: ObjectId(questions._id) // ref to questions collection by _id field
]



questions schema:




_id: ObjectId(),
text: foobar



Game could have two statuses: 'active' and 'played'.

My goal is to get all 'played' questions, means, questions, associated with games with status 'played'.



I've tried to make queries on games collection, tried to make queries on questions but none of them worked.



Some of them are:



db.games.aggregate([
$match: status: $ne: 'played',

$lookup:

from: 'questions',
localField: 'questions.questionId',
foreignField: '_id',
as: 'game_questions'

,
$project: game_questions: 1,
$unwind: path: '$game_questions', preserveNullAndEmptyArrays: false
])


Or



db.questions.aggregate([
$project: text: 1,
$lookup:
from: 'games',
pipeline: [
$match: status:'played' ,
$project: status: 1
],
as: 'game_data'

])


Bottom line:
After the request I'd like to get a list with questions, where game status is 'played'.










share|improve this question




























    1















    I have two collections: games and questions

    game schema:



     
    _id: ObjectId,
    status: 'played',
    questions:
    [
    questionId: ObjectId(questions._id) // ref to questions collection by _id field
    ]



    questions schema:




    _id: ObjectId(),
    text: foobar



    Game could have two statuses: 'active' and 'played'.

    My goal is to get all 'played' questions, means, questions, associated with games with status 'played'.



    I've tried to make queries on games collection, tried to make queries on questions but none of them worked.



    Some of them are:



    db.games.aggregate([
    $match: status: $ne: 'played',

    $lookup:

    from: 'questions',
    localField: 'questions.questionId',
    foreignField: '_id',
    as: 'game_questions'

    ,
    $project: game_questions: 1,
    $unwind: path: '$game_questions', preserveNullAndEmptyArrays: false
    ])


    Or



    db.questions.aggregate([
    $project: text: 1,
    $lookup:
    from: 'games',
    pipeline: [
    $match: status:'played' ,
    $project: status: 1
    ],
    as: 'game_data'

    ])


    Bottom line:
    After the request I'd like to get a list with questions, where game status is 'played'.










    share|improve this question


























      1












      1








      1








      I have two collections: games and questions

      game schema:



       
      _id: ObjectId,
      status: 'played',
      questions:
      [
      questionId: ObjectId(questions._id) // ref to questions collection by _id field
      ]



      questions schema:




      _id: ObjectId(),
      text: foobar



      Game could have two statuses: 'active' and 'played'.

      My goal is to get all 'played' questions, means, questions, associated with games with status 'played'.



      I've tried to make queries on games collection, tried to make queries on questions but none of them worked.



      Some of them are:



      db.games.aggregate([
      $match: status: $ne: 'played',

      $lookup:

      from: 'questions',
      localField: 'questions.questionId',
      foreignField: '_id',
      as: 'game_questions'

      ,
      $project: game_questions: 1,
      $unwind: path: '$game_questions', preserveNullAndEmptyArrays: false
      ])


      Or



      db.questions.aggregate([
      $project: text: 1,
      $lookup:
      from: 'games',
      pipeline: [
      $match: status:'played' ,
      $project: status: 1
      ],
      as: 'game_data'

      ])


      Bottom line:
      After the request I'd like to get a list with questions, where game status is 'played'.










      share|improve this question
















      I have two collections: games and questions

      game schema:



       
      _id: ObjectId,
      status: 'played',
      questions:
      [
      questionId: ObjectId(questions._id) // ref to questions collection by _id field
      ]



      questions schema:




      _id: ObjectId(),
      text: foobar



      Game could have two statuses: 'active' and 'played'.

      My goal is to get all 'played' questions, means, questions, associated with games with status 'played'.



      I've tried to make queries on games collection, tried to make queries on questions but none of them worked.



      Some of them are:



      db.games.aggregate([
      $match: status: $ne: 'played',

      $lookup:

      from: 'questions',
      localField: 'questions.questionId',
      foreignField: '_id',
      as: 'game_questions'

      ,
      $project: game_questions: 1,
      $unwind: path: '$game_questions', preserveNullAndEmptyArrays: false
      ])


      Or



      db.questions.aggregate([
      $project: text: 1,
      $lookup:
      from: 'games',
      pipeline: [
      $match: status:'played' ,
      $project: status: 1
      ],
      as: 'game_data'

      ])


      Bottom line:
      After the request I'd like to get a list with questions, where game status is 'played'.







      mongodb mongoose mongodb-query aggregation-framework






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 21:22









      Neil Lunn

      99.8k23176187




      99.8k23176187










      asked Nov 14 '18 at 16:51









      GrynetsGrynets

      1,191926




      1,191926






















          1 Answer
          1






          active

          oldest

          votes


















          2














          You can use $unwind and $replaceRoot with the data found in $lookup stage



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "let": "questions": "$questions.questionId" ,
          "pipeline": [
          "$match": "$expr": "$in": ["$_id", "$$questions"]
          ],
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])


          Or



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "localField": "questions.questionId",
          "foreignField": "_id",
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])





          share|improve this answer

























          • Any particular reason to use the first $lookup over the second?

            – Murilo
            Nov 14 '18 at 17:25











          • @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

            – Anthony Winzlet
            Nov 14 '18 at 17:39






          • 1





            Ok. Thank you :)

            – Murilo
            Nov 14 '18 at 17:52










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305153%2fselect-from-collection-a-on-clause-from-join-on-collection-b%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          You can use $unwind and $replaceRoot with the data found in $lookup stage



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "let": "questions": "$questions.questionId" ,
          "pipeline": [
          "$match": "$expr": "$in": ["$_id", "$$questions"]
          ],
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])


          Or



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "localField": "questions.questionId",
          "foreignField": "_id",
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])





          share|improve this answer

























          • Any particular reason to use the first $lookup over the second?

            – Murilo
            Nov 14 '18 at 17:25











          • @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

            – Anthony Winzlet
            Nov 14 '18 at 17:39






          • 1





            Ok. Thank you :)

            – Murilo
            Nov 14 '18 at 17:52















          2














          You can use $unwind and $replaceRoot with the data found in $lookup stage



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "let": "questions": "$questions.questionId" ,
          "pipeline": [
          "$match": "$expr": "$in": ["$_id", "$$questions"]
          ],
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])


          Or



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "localField": "questions.questionId",
          "foreignField": "_id",
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])





          share|improve this answer

























          • Any particular reason to use the first $lookup over the second?

            – Murilo
            Nov 14 '18 at 17:25











          • @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

            – Anthony Winzlet
            Nov 14 '18 at 17:39






          • 1





            Ok. Thank you :)

            – Murilo
            Nov 14 '18 at 17:52













          2












          2








          2







          You can use $unwind and $replaceRoot with the data found in $lookup stage



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "let": "questions": "$questions.questionId" ,
          "pipeline": [
          "$match": "$expr": "$in": ["$_id", "$$questions"]
          ],
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])


          Or



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "localField": "questions.questionId",
          "foreignField": "_id",
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])





          share|improve this answer















          You can use $unwind and $replaceRoot with the data found in $lookup stage



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "let": "questions": "$questions.questionId" ,
          "pipeline": [
          "$match": "$expr": "$in": ["$_id", "$$questions"]
          ],
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])


          Or



          db.games.aggregate([
          "$match": "status": "played" ,
          "$lookup":
          "from": "questions",
          "localField": "questions.questionId",
          "foreignField": "_id",
          "as": "game_data"
          ,
          "$unwind": "$game_data" ,
          "$replaceRoot": "newRoot": "$game_data"
          ])






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 15 '18 at 8:15









          Grynets

          1,191926




          1,191926










          answered Nov 14 '18 at 17:01









          Anthony WinzletAnthony Winzlet

          17.5k42045




          17.5k42045












          • Any particular reason to use the first $lookup over the second?

            – Murilo
            Nov 14 '18 at 17:25











          • @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

            – Anthony Winzlet
            Nov 14 '18 at 17:39






          • 1





            Ok. Thank you :)

            – Murilo
            Nov 14 '18 at 17:52

















          • Any particular reason to use the first $lookup over the second?

            – Murilo
            Nov 14 '18 at 17:25











          • @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

            – Anthony Winzlet
            Nov 14 '18 at 17:39






          • 1





            Ok. Thank you :)

            – Murilo
            Nov 14 '18 at 17:52
















          Any particular reason to use the first $lookup over the second?

          – Murilo
          Nov 14 '18 at 17:25





          Any particular reason to use the first $lookup over the second?

          – Murilo
          Nov 14 '18 at 17:25













          @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

          – Anthony Winzlet
          Nov 14 '18 at 17:39





          @Murilo $lookup syntax with the pipeline is a advanced version of older $lookup. It allows you to join with multiple conditions and can allow you to use all the aggregation operators. And also I do prefer more then the older one.

          – Anthony Winzlet
          Nov 14 '18 at 17:39




          1




          1





          Ok. Thank you :)

          – Murilo
          Nov 14 '18 at 17:52





          Ok. Thank you :)

          – Murilo
          Nov 14 '18 at 17:52



















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305153%2fselect-from-collection-a-on-clause-from-join-on-collection-b%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Kleinkühnau

          Makov (Slowakei)

          Peter Parker: The Spectacular Spider-Man #308