datastore

I work on an application with several microservices (modules). I defined datastore indexes in root application (which is containing just only those cfg files like datastore-indexes.xml and queue.xml etc). I see those indexes "serving" in console. [edit] so my fault i broken query earlier so question changes little. What is best strategy with mentioned cfg files in multi-module appengine app? The datastore index configuration is one of the several app-level configurations, shared by all services/modules in the app and which can be deployed independently from the services themselves. In fact it

Context: SQL Server 2008, C# I have an array of integers (0-10 elements). Data doesn't change often, but is retrieved often. I could create a separate table to store the numbers, but for some reason it feels like that wouldn't be optimal. Question #1: Should I store my array in a separate table? Please give reasons for one way or the other. Question #2: (regardless of what the answer to Q#1 is), what's the "best" way to store int[] in database field? XML? JSON? CSV? EDIT: Some background: numbers being stored are just some coefficients that don't participate in any relationship, and are always

I have an AppEngine application that I am considering upgrading to use the NDB database. In my application, I have millions of objects that have old-style db references. I would like to know what the best migration path would be to get these ReferenceProperty values converted to KeyProperty values, or any other solution that would allow me to upgrade to NDB. (I am hoping for something that doesn't involve massive batch processing of all of the elements in the database and computing the KeyProperty based on the ReferenceProperty -- something elegant would be nice) Examples of models that I

I know two ways to save/load application settings: use PersistentStore use filesystem (store, since SDCard is optional) I'd like to know what are you're practicies of working with application settings? Using PersistentStore to save/load application settings The persistent store provides a means for objects to persist across device resets. A persistent object consists of a key-value pair. When a persistent object is committed to the persistent store, that object's value is stored in flash memory via a deep copy. The value can then be retrieved at a later point in time via the key. Example of

I need to assign a unique identifier to each entity in datastore. I've found AllocateIDs but the issue is that it generates integers and I use strings for the keys. Is it safe to convert the integer to a string or there is a risk of collision (i.e. datastore to return me the same integer that I'm currently using as a string key). ? Let's clear some things first: The identifier part of an entity's key can either be a key name string or an integer numeric ID But not both. So when you save an entity, its key either has a string id called name OR (exclusive OR) an int64 id called intID . The 2

I have three entities: user , post and comment . A user may have multiple posts and a post may have multiple comments . I know I can add ancestor relations like this: user(Grand Parent) post(parent) comment(child) I'm little bit confused about ancestors. I read from documention and searches that ancestors are used for transactions, every ancestors are in same entity group and entity groups are stored in same datastore node which makes it less scaleable. Is this right? Is creating user as parent of posts and post as parent of comments a good thing? Rather than this we can add one extra property