Oh also, I thought OneToOneFields were discouraged in favor of
ForeignKeys with unique=True as per
http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
Thanks for the help guys. Splitting the models up was mostly a
cosmetic thing for the admin, but these problems quickly kicked me out
of that state. Anyway, yes, the database design is really bad, mostly
because that's not what the game developers are experts at
unfortunately.
--~--~-~--
Bryan Veloso skrev:
(I am only commenting on the model (database and Django) in this post -
I don't really know enough about imports to help you with that bit)
> I have 2 models for an MMORPG control panel I'm building. Each set of
> data is within it's own app with related models, etc. So here'
On Wed, 2007-07-04 at 23:06 +, Bryan Veloso wrote:
> I don't know if this is even possible, since I've had so many errors
> thrown at me, but I wanted to ask here so I can get a clear picture.
>
> I have 2 models for an MMORPG control panel I'm building. Each set of
> data is within it's own
I don't know if this is even possible, since I've had so many errors
thrown at me, but I wanted to ask here so I can get a clear picture.
I have 2 models for an MMORPG control panel I'm building. Each set of
data is within it's own app with related models, etc. So here's my
example. It's run off
5 matches
Mail list logo
