There is no such thing as getting only one property. Big Table is not
a relational database. When you get a match for any query you get
back a full object. Your db classes are just that: classes. There is
no such thing as a class instance variable without the class. You
cant get an instance variable without an instance. It doesn't make
any sense. It sounds a lot like you have designed your models in the
old relational way instead of the object way. I did the same thing on
my first 2 App Engine apps and had to redo them once I figured out how
to stop thinking relationally. Your ReferenceProperty idea will work
as expected and not load unless asked for but your design seems
flawed. If you have an entity with 60 properties and you only want 1
than your still thinking relationally and it won't scale (as you have
already found out).
Perhaps if you can provide a bit more information on your model, what
you are trying to do and how your view is related someone can provide
some better feedback for you. Remember always that you should design
your models based on your views so that they match up as closely as
possible.
Mike
On Sep 11, 8:41 am, GAEfan <[EMAIL PROTECTED]> wrote:
> Perhaps, instead of:
>
> myData.all().filter("some filter expression")
>
> I can hack the all() function to parse to a single property, so I can
> do a:
>
> myData.all('EmailAddress').filter("some filter expression")
>
> Where is this all() function located?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
