Yeah, the tutorial is right here:
http://www.bitbucket.org/DeadWisdom/migratory/wiki/Tutorial
On Fri, Jan 2, 2009 at 6:57 PM, Yuri Baburov wrote:
>
> Could you please write some tutorial on your page, how does the
> migration process looks like with your app?
>
> On Sat, Jan 3, 2009 at 2:29 AM,
Could you please write some tutorial on your page, how does the
migration process looks like with your app?
On Sat, Jan 3, 2009 at 2:29 AM, Brantley Harris wrote:
>
> Having not been content with the state of Django migrations systems,
> I've created one of my own:
>
> http://www.bitbucket.org/D
Having not been content with the state of Django migrations systems,
I've created one of my own:
http://www.bitbucket.org/DeadWisdom/migratory/
The idea is a database migration system that:
* Is simple.
* Doesn't make you use sql. This is an orm, we shouldn't have to use sql.
* Can b
I can confirm this based on the source, the issue is at line 206 here:
http://code.djangoproject.com/browser/django/trunk/django/contrib/contenttypes/generic.py#L199
self.field.model refers to the field.model refers to the original
model that was set when contribute_to_class() was called on the ba
Hi,
The easiest way to explain this is with code I guess:
http://dpaste.com/104502/
These are the models for a contact management application. Basicly I
have a "Contact Model", which is used to hold details for both the
"Person" and "Company" Models. On the "Contact Model" I have some
generic re
