> 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.
You don't have to run propel-insert-sql for your symfony app to work. But your schema.yml must match your database or else it won't work. On Thu, Apr 2, 2009 at 1: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... > > > > -- Blue Horn Ltd - System Development http://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
