Access to ForeignKeyField's related_name attribute from another process?
This sounds very evil.
 Without sounding pedantic, could you elaborate on the ambiguous pronoun "this"? That is, are you saying that model sharing across processes is evil or that attribute level model accessor affordances existing across processes is evil? If so, why? This seemed like a perfectly reasonable use of peewee to me.
 a peewee model is just a class...changes made in one python interpreter will not affect another interpreter process.  if you need to, shuffle messages around via IPC that do the attribute manipulation.

i said it was evil because a related_name is really an internal API used by code, so i was confused why code would need to change it.
 when you get a chance, please update me with the status of this or provide more info so i can help resolve
 In the example below, D is the model class representing the related_name d which was being used to access the values from the downstream process. This is, of course, broken, as you pointed out, because the downstream process hasn't manifested the attributes like the upstream process. Thus, this breaks because the related_name attribute d doesn't exist:

a.b.c.d[0].e

The solution is to use a get query in place of the missing related_name attribute:

D.get(c=self.a.b.c).e

which works fine.

This is, of course, writ large to show the relationships. The actual code uses functional shorthand to flatten the joins. 

I thought this might be a useful piece of documentation. Perhaps obvious, but wasn't immediately apparent to me until I thought through the related_name issue. It seemed from your earlier answer that related_name may be intended for internal use only. Should I never be using related_name attributes outside the model they're defined in?

I wanted to point this out, because, while my use of peewee maybe somewhat beyond its intended usage, these things can and do work. And I love peewee!
 Hmm... I suppose I'm still not 100% sure what the related name issue is.  Can we talk about two of my favorite models, User and tweet (which Fks to user)?

``` python

class User(Model):
    username = CharField()

class Tweet(Model):
    user = ForeignKeyField(User, related_name='tweets')
    message = CharField()
```

Can you show me, using those two models, the issue?
 Yeah, no problem.

The first process creates a user which has associated tweets. The second process needs to act on a user's associated tweets but the tweets related_name doesn't exist:

Process #1: 

user.tweets

Process #2:
user = User.get(username="charlie")
Tweet.get(user=user)
 closing for now

I have several processes that share the same peewee models. One of those processes manipulates data which effects a ForeignKeyField's related_name attribute which is then later accessed by another process. However, accessing the attribute throws a missing attribute exception from the downstream process. Is it possible to instantiate this attribute in the second process? If so, how?

Thanks.
