Cool. I'm going the same thing (DDL diffs) tonight or tomorrow with the
SQLite stuff first, and then PosgreSQL. We'll get this knocked out!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To po
Hi Ken,
Ken Kennedy wrote:
> You may want to compare those field sizes to a "clean" install of
> M-R...if I remember correctly, one or both have been increased in size
> in a new install. We'll need to make sure that migrated field sizes
> match newly created ones, or we'll end up with WEIRD erro
You may want to compare those field sizes to a "clean" install of
M-R...if I remember correctly, one or both have been increased in size
in a new install. We'll need to make sure that migrated field sizes
match newly created ones, or we'll end up with WEIRD errors that only
occur with migrated dat
Hi Ken,
Ken Kennedy wrote:
> At this point, the various differences in SQL capabilities between the
> backends have resulted in a split of the migration DDL/DML into a
> separate list for each engine. I'm working on tweaking them, but I'll
> probably get to MySQL last, so feel free to pitch in!
At this point, the various differences in SQL capabilities between the
backends have resulted in a split of the migration DDL/DML into a
separate list for each engine. I'm working on tweaking them, but I'll
probably get to MySQL last, so feel free to pitch in!
--~--~-~--~~---
Graham King wrote:
> In the RemovingTheMagic wiki page, the MySQL for upgrading the database
> has these two lines:
>
> ALTER TABLE django_content_type rename package to app_label;
> ALTER TABLE django_content_type rename python_module_name to model;
>
> In MySQL 4.1.14 (and in the docs
In the RemovingTheMagic wiki page, the MySQL for upgrading the database
has these two lines:
ALTER TABLE django_content_type rename package to app_label;
ALTER TABLE django_content_type rename python_module_name to model;
In MySQL 4.1.14 (and in the docs for MySQL 5.0), the commands s
7 matches
Mail list logo
