On Friday 18 June 2010 14:07:53 Tom Evans wrote:
> On Fri, Jun 18, 2010 at 9:03 AM, Kenneth Gonsalves
wrote:
> > On Friday 18 June 2010 07:27:10 Shawn Milochik wrote:
> >> Use South data migrations.
> >
> > I do not understand what data migration has to do with this.
>
> Data fixups are one sort
I'm assuming there's no fields on the duplicate player instances that
need merging - from your mention of "shift all records of the
duplicate" I'm reading that as "shift all records that relate to the
player" - otherwise it will need human intervention. Having stated
that assumption, while it's pos
On Fri, Jun 18, 2010 at 9:03 AM, Kenneth Gonsalves wrote:
> On Friday 18 June 2010 07:27:10 Shawn Milochik wrote:
>> Use South data migrations.
>>
>
> I do not understand what data migration has to do with this.
Data fixups are one sort of migration - its not a schema migration,
but a data migrat
On Friday 18 June 2010 07:27:10 Shawn Milochik wrote:
> Use South data migrations.
>
I do not understand what data migration has to do with this.
--
Regards
Kenneth Gonsalves
Senior Associate
NRC-FOSS at AU-KBC
--
You received this message because you are subscribed to the Google Groups
"Dja
Use South data migrations.
Sent from my iPad, in accordance with the prophesy.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
hi
I have a problem - there is a model called Player with first_name and
last_name. There is a unique_together constraint on first_name and last_name.
However I find that the people doing data entry have been entering things like
Ram Sharan and RAM SHARAN which are two different names. Of cours
6 matches
Mail list logo
