Closed GoogleCodeExporter closed 9 years ago
This is actually a fairly common issue. I work a lot with Django, which suffers
from
the same problem. Database migration is a fairly resource intensive thing to
do, in
my opinion. I say you shouldn't generally need to change tables on the fly.
Original comment by ScottALyons
on 17 Jan 2009 at 7:40
I'd also expect the table to automatically update with an appropriately new
column, so that Version 1.1 can be
released with a column added in some table.
Original comment by janeblit...@gmail.com
on 4 Feb 2009 at 2:50
But this could be used for iphone apps. If v2 of the app changes the table
structures then how should this work - not got to that point with my apps :)
but
presumably the v2 app will see the v1 db after being upgraded... Should it use
new
tables and do the migration itself first time through?
Original comment by kimptoc
on 4 Feb 2009 at 7:56
The problem is, what do you fill in to the already existing rows. I would like
to see the ability to have a default
for each property (which would need to also make it through to the init
function) so that this could be used to
populate correctly.
Original comment by mattjgal...@gmail.com
on 17 Feb 2009 at 5:28
I have added a consistency check that will alter the table and add a column for
any missing properties. Please
test when yo have a chance.
Original comment by jeff.lam...@gmail.com
on 19 Feb 2009 at 1:06
Can't seem to find the revision which this was fixed in? Where did it go Jeff?
Original comment by mattjgal...@gmail.com
on 25 Feb 2009 at 10:31
Original issue reported on code.google.com by
gonz...@gmail.com
on 7 Jan 2009 at 10:43