1) If you have no other schema changes a simpler solution would be to
just change all your table names manually to lower.
2) Hook the new version to a blank db and let it generate a dummy sql
table. swap the table with the one you changed the table names in step
1 -> after turning off web2py i.e.
--
Praneeth
IRC: lifeeth
On Thu, Apr 21, 2011 at 12:32 AM, robe...@captivation.com
<gummywubb...@gmail.com> wrote:
> Hi Everybody,
>
> Yesterday evening I ran into some issues updating an app from 1.89.6
> to 1.94.5 -- specifically with case sensitivity in migrating tables.
> This occurs on an ubuntu ec2 instance, running mysql as installed by
> 'aptitude install mysql-server' and accepting defaults.
>
> An example.
>
> The field is defined in models with
>
> Field('splatToken'),
>
> The .table file before the migration contains
>
> p9
> sS'splatToken'
>
> The .table file after the first execution contains
>
> p9
> sS'splattoken'
>
> The next execution yields an exception in DAL.py migrate_table
> triggered off this test:
> and not isinstance(table[key].type, SQLCustomType) \
>
> I was able to bypass the issue and continue by removing the .lower()
> calls in the sql_fields* assignments up above.
>
>
> So, my app is running as it needs to be, but this really feels like a
> band-aid and incorrect solution. In searching this groups archives,
> I've seen some similar issues, but they all seem to have been resolved
> a few months ago.
>
> Advice? Thoughts? Questions?
>
> Cheers,
> :R
>
>
>
>
