Quenten Griffith wrote: > I usually do the database work in MySQL first and then update the schema > file with symfony propel-build-schema xml. I find it easier to create > tables in MySQL then typing them in the schema files, plus you don't > lose any data when you do this.
It would be nice if Propel/Doctrine could introspect the installed schema, compare it with the updated schema and then generate (and optionally execute) SQL alter statements. However introspection is always tricky, so in order to make this even more reliable (and easier), one could also maintain a meta table, which stores the version of the schema (and options that affect SQL schema generation) inside a table in the database. Instead of doing on the fly introspection, it would then read the data from the database. regards, Lukas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
