Hello,
Can you provide samples form your model definitions? It would make it
much easier to follow what you're trying to do.
On Feb 24, 12:01 pm, simpsus_science wrote:
> Hallo,
>
> I read up the solution for implementing 1:n relationships by placing a
> ReferenceProperty on the "n" part and nam
Don't type the ReferenceProperty.
You've got to be careful though. If you have A ref'ing B and B
ref'ing A, it's very easy to get stuck in a loop. (Anything that
recurses over the item's properties, like a for loop or the Django
debug page, will implicitly get the entity instead of the key for
Thanks for your replies.
On 24 Feb., 20:02, theillustratedlife wrote:
> Don't type the ReferenceProperty.
You mean subclassing the ReferenceProperty? I don't want to do that.
Otherwise, I don't understand what you mean...
>
> You've got to be careful though. If you have A ref'ing B and B
> ref'
This is a minimal example of the stuff that I want to do.
class PMethod(PElement):
body = db.StringProperty()
class PElement(PolyModel):
name = db.StringProperty()
pMethodInput = db.ReferenceProperty(MetaPMethod,
collection_name='input')
pMethodOutput = db.ReferenceProperty(MetaP
> class PElement(PolyModel):
> name = db.StringProperty()
> pMethodInput = db.ReferenceProperty(collection_name='input')
> pMethodOutput = db.ReferenceProperty(collection_name='output')
^That's what I mean by not typing the RP.
--~--~-~--~~~---~--~~
You
