On Thu, Mar 28, 2013 at 6:50 AM, Tom Evans wrote:
> This should be many migrations, not one migration.
>
> 1) Schema migration: Add nullable foreign key to Project to CCD.
> 2) Data migration: Create Project objects as needed from 'RMversion' links
> 3) Data migration: Update CCD objects to point
On Wed, Mar 27, 2013 at 11:49 PM, Tim Cook wrote:
> I can't find a similar scenario in the list archives, so .
>
> I had run the initial migration, etc and all seemed fine.
>
> I modified one model from this:
> class CCD(models.Model):
> rm_version = models.ForeignKey(RMversion,
> related
do 0001 --fake, your table south_migrations dont have the row indicating
that initial
On Wed, Mar 27, 2013 at 8:49 PM, Tim Cook wrote:
> I modified one model from this:
--
juanpex
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsu
I can't find a similar scenario in the list archives, so .
I had run the initial migration, etc and all seemed fine.
I modified one model from this:
class CCD(models.Model):
rm_version = models.ForeignKey(RMversion, related_name='%(class)s_related+')
...
to this:
class CCD(models.Mod
4 matches
Mail list logo
