Migration of PKs to 1.0

[jcorrie]

I have been upgrading a legacy project to 1.0. One change for 1.0 is "Generated code now uses 64-bit primary keys". As the migration guide says, this only affects new models created post-migration.

The issue I have had is that because the migration files refer to ColType::PkAuto (which has shifted from 32 to 64-bit), when I run migrations for a fresh db, for example in dev or test, that fresh db now builds columns expecting 64-bit data. That gives me a mismatch between the code (32-bit) and the db (64-bit). A legacy dev db that I had built already still works (and so presumably prod will still work if I were to push the code change),.

Is this expected behaviour or have I gone about the 1.0 upgrade in the wrong way?

[jcorrie]

@jondot - would you mind taking a quick look at this?