On Nov 3, 8:31 am, "David Symonds" <[EMAIL PROTECTED]> wrote: > > Kind --> it's really a class, a specialization of the db.Model or > > db.Expando classes. > > Not quite. An entity may look like an instance of a Kind when accessed > through the db.Model layer, but it isn't fundamentally a specific > Kind. For instance, the Key-space is across all entities of your > datastore, not of a particular kind. Also, if you change your > db.Model, existing entities aren't changed automatically.
Coolio and agreed - I've stuck with the term "entity" for that reason. What about other places where App Engine seems to have its own terminology for Python/OO concepts? In general I'm going with: 1. If it's clear that this is a something specific to App Engine (like your example), use App Engine terms 2. If it's what appears to be a generic Python term renamed, use the Python term (e.g. decorator instead of annotation unless the decorator actually annotates the code!) 3. If it's neither of the above, find a generic OOP/OOD term that applies depending on context and intended meaning Thanks Dave and have a great day! E http://www.istheserverup.net http://www.teslatestament.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
