Does TypeOrm automatically assign foreign keys on insert?










0















I am curious if I am doing something wrong. I have entities defined with OneToMany relationships. They are:



Category
CategoryItem


with Category being the top level and OneToMany relationships between CategoryItem.



When creating new records I do:



const newCategory: Category = new Category();
newCategory.name = 'Bob'
newCategory.items = ;

const newItem: CategoryItem = new CategoryItem();
newItem.someField = 'whatever';

newCategory.items.push(newItem);


Now, when I go to save these items, if I just do:



(note: entities in the below code is a getManager() call result)



await entities.save(category)


Then the category is saved, but the categoryItems are not saved. (aren't they supposed to be)?



If I do



await entities.save(category);
for(const item of category.items)
await entities.save(item);



Then I get an error saying cannot insert null into categoryId field for the CategoryItem records. In order for it to save correctly, I find I have to do this:



await entities.save(category);
for(const item of category.items)
item.categoryId = category.categoryId;
await entities.save(item);



only then will it save.



This is not what I expected to happen. I expected that the child items would be saved, and have their foreign key fields automatically matched up.



Am I wrong in this expectation? If not, any thoughts on what I might be doing wrong?










share|improve this question


























    0















    I am curious if I am doing something wrong. I have entities defined with OneToMany relationships. They are:



    Category
    CategoryItem


    with Category being the top level and OneToMany relationships between CategoryItem.



    When creating new records I do:



    const newCategory: Category = new Category();
    newCategory.name = 'Bob'
    newCategory.items = ;

    const newItem: CategoryItem = new CategoryItem();
    newItem.someField = 'whatever';

    newCategory.items.push(newItem);


    Now, when I go to save these items, if I just do:



    (note: entities in the below code is a getManager() call result)



    await entities.save(category)


    Then the category is saved, but the categoryItems are not saved. (aren't they supposed to be)?



    If I do



    await entities.save(category);
    for(const item of category.items)
    await entities.save(item);



    Then I get an error saying cannot insert null into categoryId field for the CategoryItem records. In order for it to save correctly, I find I have to do this:



    await entities.save(category);
    for(const item of category.items)
    item.categoryId = category.categoryId;
    await entities.save(item);



    only then will it save.



    This is not what I expected to happen. I expected that the child items would be saved, and have their foreign key fields automatically matched up.



    Am I wrong in this expectation? If not, any thoughts on what I might be doing wrong?










    share|improve this question
























      0












      0








      0








      I am curious if I am doing something wrong. I have entities defined with OneToMany relationships. They are:



      Category
      CategoryItem


      with Category being the top level and OneToMany relationships between CategoryItem.



      When creating new records I do:



      const newCategory: Category = new Category();
      newCategory.name = 'Bob'
      newCategory.items = ;

      const newItem: CategoryItem = new CategoryItem();
      newItem.someField = 'whatever';

      newCategory.items.push(newItem);


      Now, when I go to save these items, if I just do:



      (note: entities in the below code is a getManager() call result)



      await entities.save(category)


      Then the category is saved, but the categoryItems are not saved. (aren't they supposed to be)?



      If I do



      await entities.save(category);
      for(const item of category.items)
      await entities.save(item);



      Then I get an error saying cannot insert null into categoryId field for the CategoryItem records. In order for it to save correctly, I find I have to do this:



      await entities.save(category);
      for(const item of category.items)
      item.categoryId = category.categoryId;
      await entities.save(item);



      only then will it save.



      This is not what I expected to happen. I expected that the child items would be saved, and have their foreign key fields automatically matched up.



      Am I wrong in this expectation? If not, any thoughts on what I might be doing wrong?










      share|improve this question














      I am curious if I am doing something wrong. I have entities defined with OneToMany relationships. They are:



      Category
      CategoryItem


      with Category being the top level and OneToMany relationships between CategoryItem.



      When creating new records I do:



      const newCategory: Category = new Category();
      newCategory.name = 'Bob'
      newCategory.items = ;

      const newItem: CategoryItem = new CategoryItem();
      newItem.someField = 'whatever';

      newCategory.items.push(newItem);


      Now, when I go to save these items, if I just do:



      (note: entities in the below code is a getManager() call result)



      await entities.save(category)


      Then the category is saved, but the categoryItems are not saved. (aren't they supposed to be)?



      If I do



      await entities.save(category);
      for(const item of category.items)
      await entities.save(item);



      Then I get an error saying cannot insert null into categoryId field for the CategoryItem records. In order for it to save correctly, I find I have to do this:



      await entities.save(category);
      for(const item of category.items)
      item.categoryId = category.categoryId;
      await entities.save(item);



      only then will it save.



      This is not what I expected to happen. I expected that the child items would be saved, and have their foreign key fields automatically matched up.



      Am I wrong in this expectation? If not, any thoughts on what I might be doing wrong?







      typeorm






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 14:41









      Clever HumanClever Human

      6,12524465




      6,12524465






















          0






          active

          oldest

          votes











          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%2f53283468%2fdoes-typeorm-automatically-assign-foreign-keys-on-insert%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          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%2f53283468%2fdoes-typeorm-automatically-assign-foreign-keys-on-insert%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

          27

          Top Tejano songwriter Luis Silva dead of heart attack at 64

          Category:Rhetoric