1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
<br><br><div class="gmail_quote">On 15 March 2011 09:14, Romain d'Alverny <span dir="ltr"><<a href="mailto:rdalverny@gmail.com">rdalverny@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<div class="im"><br>
On Tue, Mar 15, 2011 at 01:02, Kosmas Chatzimichalis <<a href="mailto:Kosmas@mach7x.com">Kosmas@mach7x.com</a>> wrote:<br>
> Just pulled your changes.<br>
> Looks nice !<br>
<br>
</div>Thanks.<br>
<div class="im"><br>
> As it is the beginning of the app, wouldn't be better to recreate the tables<br>
> with only the necessary fields, instead of adding migrations that only<br>
> remove the fields?<br>
<br>
</div>I wondered, yes, because that makes a lot of things to move around,<br>
although the end result would be about the same (hopefully, I managed<br>
the spackage=>package renaming withouth breaking too much). Would you<br>
just recreate the tables or just remake the app from scratch, porting<br>
only the new portions of code needed?<br></blockquote><div> <br> We won't need to make any changes to the actual application.<br> We can put all the changes to the original migration, then remove all the tables (migrate down the database), and then run the migration again to create the new tables. So the whole of the application wouldn't need any change at all.<br>
If you agree I can do that, don't worry about it.<br> <br>For the spackage renaming, it was there to distinguish it from the compiled packages and to be one word that sometimes make it easier. <br>Since we do not need the compiled packages any more, we can simply call that packages.<br>
</div></div>So maybe we can also change it to be only packages.<br>Not a big change again, but we will need to change model,views, controllers.<br>
|
