DynamoDB schema updates with AWS Amplify











up vote
1
down vote

favorite












According to the AWS Amplify documentation:




  • "objects annotated with @model are stored in Amazon DynamoDB";

  • "a single @model directive configures ... an Amazon DynamoDB table"; and

  • one can "push updated changes with amplify push".


It seems clear that amplify push creates a DynamoDB table for each @model.



My questions relate to schema updates:




  • I imagine that adding/removing a model or adding/removing a field in a model works by updating the schema document and then running amplify push. Is that right?


  • How does one rename a model or a field? How would amplify push know to rename vs. drop the old and add the new?


  • How does one implement a migration that requires some business logic, e.g., to update the contents of existing rows? Doing this without Amplify has already been addressed but it is unclear whether that would conflict with something that amplify push might try to do.







amazon-web-services amazon-dynamodb graphql database-migration aws-amplify







share|improve this question


























    up vote
    1
    down vote

    favorite












    According to the AWS Amplify documentation:




    • "objects annotated with @model are stored in Amazon DynamoDB";

    • "a single @model directive configures ... an Amazon DynamoDB table"; and

    • one can "push updated changes with amplify push".


    It seems clear that amplify push creates a DynamoDB table for each @model.



    My questions relate to schema updates:




    • I imagine that adding/removing a model or adding/removing a field in a model works by updating the schema document and then running amplify push. Is that right?


    • How does one rename a model or a field? How would amplify push know to rename vs. drop the old and add the new?


    • How does one implement a migration that requires some business logic, e.g., to update the contents of existing rows? Doing this without Amplify has already been addressed but it is unclear whether that would conflict with something that amplify push might try to do.







    amazon-web-services amazon-dynamodb graphql database-migration aws-amplify







    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      According to the AWS Amplify documentation:




      • "objects annotated with @model are stored in Amazon DynamoDB";

      • "a single @model directive configures ... an Amazon DynamoDB table"; and

      • one can "push updated changes with amplify push".


      It seems clear that amplify push creates a DynamoDB table for each @model.



      My questions relate to schema updates:




      • I imagine that adding/removing a model or adding/removing a field in a model works by updating the schema document and then running amplify push. Is that right?


      • How does one rename a model or a field? How would amplify push know to rename vs. drop the old and add the new?


      • How does one implement a migration that requires some business logic, e.g., to update the contents of existing rows? Doing this without Amplify has already been addressed but it is unclear whether that would conflict with something that amplify push might try to do.







      amazon-web-services amazon-dynamodb graphql database-migration aws-amplify







      share|improve this question













      According to the AWS Amplify documentation:




      • "objects annotated with @model are stored in Amazon DynamoDB";

      • "a single @model directive configures ... an Amazon DynamoDB table"; and

      • one can "push updated changes with amplify push".


      It seems clear that amplify push creates a DynamoDB table for each @model.



      My questions relate to schema updates:




      • I imagine that adding/removing a model or adding/removing a field in a model works by updating the schema document and then running amplify push. Is that right?


      • How does one rename a model or a field? How would amplify push know to rename vs. drop the old and add the new?


      • How does one implement a migration that requires some business logic, e.g., to update the contents of existing rows? Doing this without Amplify has already been addressed but it is unclear whether that would conflict with something that amplify push might try to do.







      amazon-web-services amazon-dynamodb graphql database-migration aws-amplify




      amazon-web-services amazon-dynamodb graphql database-migration aws-amplify






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      kkurian

      1,99032236




      1,99032236





























          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',
          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%2f53372696%2fdynamodb-schema-updates-with-aws-amplify%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372696%2fdynamodb-schema-updates-with-aws-amplify%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

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d
          Read more

          SQL update select statement

          Image
          0 I'm trying to update an entry in my database (postgresql). I'm having a problem with updating the query: INSERT INTO prices (price, product_id) SELECT product_price, commn_id FROM products_temp as prod WHERE NOT EXISTS (SELECT * FROM prices od WHERE prod.commn_id = od.product_id) OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) Query works fine when i delete: OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) So it seems to me that it's looping through this operation. My question is, how can I fix it? sql postgresql
          Read more

          'app-layout' is not a known element: how to share Component with different Modules

          Image
          0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule
          Read more