Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7712293
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T01:35:38+00:00 2026-06-01T01:35:38+00:00

I am migrating an app to the High-Replication datastore. The way I understand that

  • 0

I am migrating an app to the High-Replication datastore. The way I understand that works is that I simply copy my data to a new app that has the HRDS enabled, using the Datastore Admin.

However, my app has some entities that link to other entities by means of their key.ids.

posts = db.ListProperty(int)

When I migrate the app, the ID’s of objects are likely to change, no? How do I ensure that these lists still link properly?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T01:35:39+00:00Added an answer on June 1, 2026 at 1:35 am

    Using the datastore migration tool (as Daniel suggests), existing entity IDs will be preserved.

    You really should be using lists of keys rather than IDs, though.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Following these instructions: http://neogregious.blogspot.com/2011/04/migrating-app-to-high-replication.html I have managed to migrate to the high replication datastore
I'm working on migration of data from a legacy system into our new app(running
I'm migrating an old app that uses application.cfm to use an application.cfc. The CFM
I'm migrating a WinForms app to WPF. Everything has gone well so far except
I am migrating a classic ASP web app to new servers. The database back
I am migrating my old FB app to the new graph API using the
is there any documentation on changes that i might hit when migrating an app
I'm migrating my gae app to python 2.7. This is my new app.yaml: application:
My app has a potentially very large CoreData datastore underneath it (could easily be
I have an app that I am migrating from Ruby to JRuby (due to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.