Existing ndb data -> Python 3 data

[Bruce Sherwood]

I've seen the documentation on Python 3 datastores, but what I haven't seen is how to deal with preserving existing user data.

My existing GAE (Python 2.7, standard environment, ndb) has 60,000 user records. Perhaps one way to preserve this data would be to add code to my current Python server to dump the data in a format I understand, switch GAE to use the new datastore mechanism, then have the server upload my data and place the data into the new datastore.

However, I'm surely not the only person facing this challenge, so is there some other/better approach?

Bruce

[Rahul Ravindran]

Development of the new Python 3-compatible ndb client is happening in the Google Cloud Python client library github repo at https://github.com/googleapis/google-cloud-python/tree/master/ndb . The library is not usable as-is yet, but work is in progress and can be monitored there.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e1ab0052-3f6a-4d41-a98c-4a88c5d42adf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bruce Sherwood]

That is very good news indeed. It's not immediately obvious from that site's Migration document whether the new ndb library is intended just to be something that will make it easy for someone familiar with the existing ndb library to build a new GAE, or rather that the intent is to make it possible for people like me to access an existing ndb database in an old GAE whose Python 2.7's server is replaced by a Python 3 server. Can I assume that one of the goals is to be able to use an old ndb database?

[Rahul Ravindran]

That is the idea. I encourage you to participate in the early releases etc to ensure your use case is being met. You may have additional steps to enable caching.

On Tue, Feb 12, 2019 at 5:30 PM Bruce Sherwood <bruce.s...@gmail.com> wrote:

That is very good news indeed. It's not immediately obvious from that site's Migration document whether the new ndb library is intended just to be something that will make it easy for someone familiar with the existing ndb library to build a new GAE, or rather that the intent is to make it possible for people like me to access an existing ndb database in an old GAE whose Python 2.7's server is replaced by a Python 3 server. Can I assume that one of the goals is to be able to use an old ndb database?

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f4d2ee37-3714-4af9-88f7-5ba6f68b56b7%40googlegroups.com.