Alternatively, you can just skip the insert task, and selectively grab tables from the generated sql definitions in /data/sql/.. Paste those into mysql, and you got a new table as well. As for "modifying" existing tables, that would truly fall under migration, and unfortunately it involves some manual updates.. That could indeed be improved.
Daniel On Apr 27, 7:06 pm, Parijat Kalia <kaliapari...@gmail.com> wrote: > For the past 5 days, I have been trying to find a healthy solution to the > migrations issue that we propellers tend to face. Apparently, whenever you > create a new database table or make changes to an existing database table, > you will make the changes/additions to the *schema.yml* and you are going to > call upon the > > *build-all command.* > > This encapsulates, *build-schema, build-sql, insert-sql, > build-model*commands. The > *build-sql and insert-sql* commands will essentially reconstruct the > database tables from scratch, after having dropped the existing ones. > > This is a painful thing, and it sucks that there is no provision for this > that is in built with symfony, since ppl are always gonna update databases > and tables, delete them and remove them as and when the project progresses. > > You need to get sfPropelMigrationsLightPLugin (which handles basic > migrations, and I never figured out how to isntall it correctly), and play > along with it. > > So after almost giving up, here's what I tried today: > > 1. Create the db table by hand in your phpmyadmin, or whatever db u > use...using the GUI interface > 2. run build-schema to make the schema.yml file imitate the existing file > 3. run build-model to make the necessary model for the file > 4. symfony clear cache > > no need for build-sql and insert-sql and don't run build-all at all. > > And Voila, you have your database table ready without dropping a single > instance from your existing tables. > > if anyone has done this before, and know's of errors, let me know > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/symfony-users?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
