Rafe, do you think we'll be seeing a db.ModelMixin anytime in the near
future?
On 11 March 2010 10:01, Rafe wrote:
> The built-in property classes are not likely to change in future
> releases. I've already written an article about extending properties
> and am loath to break peoples existing
The built-in property classes are not likely to change in future
releases. I've already written an article about extending properties
and am loath to break peoples existing applications (even though it
sometimes happens by mistake - and we then revert those changes):
http://code.google.com/ap
c...@your solution, PK!
Since db.PropertiedClass is not documented in the official docs, I'm
assuming there's a chance that its implemented could change in future
releases, and possibly break your code yeah?
Can someone from Google please comment on whether db.PropertiedClass is
"concrete" enough
Thanks PK, I'll check it out now.
Nick
On 5 March 2010 19:41, PK wrote:
> Hi Nick,
>
> I have been using the pattern described by Rafe very successfully in
> my app. Regarding the problem you are desribing I have written up how
> I solved the problem here:
>
> http://www.gae123.com/articles/td
Hi Nick,
I have been using the pattern described by Rafe very successfully in
my app. Regarding the problem you are desribing I have written up how
I solved the problem here:
http://www.gae123.com/articles/tds/model-mixin.html
Read the whole page for the details or just scroll to the bottom for
Using non-Model mix-ins worked a treat. Thanks again Rafe.
There is one small problem I'm hoping you can help me with (again). It's not
a show-stopper because I can work around it, however I'm hoping you'd know
of a nicer way to do this. Note that it's not only specific to PolyModel,
but to db.Mod
Thanks for your reply Rafe. Using non-Model mix-ins seems like the way to
go.
As with many App Engine developers, my Python experience is equivalent to my
App Engine experience, so I appreciated the Python lesson ;)
Nick
On 5 March 2010 08:52, Rafe wrote:
> There is currently no proper way t
There is currently no proper way to do "re-root" a polymodel the way
you are describing. However, there may be a solution for your
particular problem. I don't know enough about your actual
implementation however you might get away with simply doing a non-
Model based mix-in. So, write your mem
I should state that I can set the entity kind that's saved in the
Datastore by adding a kind() method on my "real" models, however the
class list property of the saved entities still includes the "special"
PolyModel subclass in it, and I'm not sure if that's a bad thing or
not.
On Mar 4, 2:16 pm,
