Re: [google-appengine] Select columns

Hi Ikai, I did read the documentation and now I have my data structures in place. One thing I wanted to do and that was not clear from my previous post was to append a app generated string (not unique) as a prefix to a datastore generated key. For instance, I want to generate a key that has the d

Re: [google-appengine] Select columns

Have you read our documentation on KeyFactory? http://code.google.com/appengine/docs/java/datastore/relationships.html I'd try to understand what's going on there. It sounds like you're doing it the right way, but it's up to

Re: [google-appengine] Select columns

Ikai, Based on your inputs I created two data classes that have a unidirectional one-to-one relationship Now, I have two data classes simpledata and detailscol. simpledata contains fields A, B, C (and a Key field) detailscol just contains field D. simpledata imports detailscol that contains field

Re: [google-appengine] Select columns

Thanks guys for clearing up my confusion. Thanks Ikai for pointing me to the documentation as well. I will read up on the documentation and if I have any more questions will bug you guys again :). Manny On Sat, Jan 30, 2010 at 12:16 AM, Ikai L (Google) wrote: > Hi Manny, > > A few things to fi

Re: [google-appengine] Select columns

Hi Manny, A few things to first remember - App Engine's datastore is not a database, but a distributed key value store with additional features. Thus, we should be careful not to frame our thinking in terms of RDBMS schemas. For this reason, I like to avoid using database terminology that can conf

Re: [google-appengine] Select columns

You are on the right track with your second idea. Create a separate kind for 'D'. I am not familiar enough with the semantics of GAE-Java to suggest a specific implementation. In GAE-Python I would make the kind with A, B, C the parent of the kind containing D, that would allow me to reconstruct

[google-appengine] Select columns

Hi All, First off, thanks for your time. A quick noob question on the right way to model data. I have a table with four columns A,B,C, D. D - the fourth is of type text (contains quite a bit of data). I wanted to ensure that the contents of the details column 'D' is not fetched during a query.