If your schema.yml file already matches your database schema then run propel-build-model to update your symfony application to create the model files for any missing tables in your database. I had to do this a while back where I manually edited the database schema, added the new table information into my schema.yml then ran (I am on symfony 1.1) propel:build-model.
Gareth On Thu, Apr 2, 2009 at 11:28 PM, Atznt <[email protected]> wrote: > > We have a BIG problem. It seems the task propel-insert-sql MUST BE > DONE, in order to acces to our database right on. Our Database already > exists and is populated with information extremly sensitive, therefore > that task will ERASE and recreate tables. > > There is no way touching (except for DDL) the database, What else > should We do? > > I hope We are on mistake... and there is solution to this. > > Thanks in advance... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
