If you set different package property in the database tag you will end with deferments sql files, but you have to run thous sql against the database yourself (propel will run all). You could run propel-build-sql every time you have a to build the sql and get a custom sql according with your schemas configuration (ie the files you included in that particular proyect), and also with your database backend witch could be a plus.
On 10/25/07, Eno <[EMAIL PROTECTED]> wrote: > > Is there a way to split the schema.xml file into several smaller XML > files and tell Propel what filenames to use for the generated SQL > files? We have lot of sub-sites that share the same code tree but need > individual schema. I tried making an extra XML file and it works > (assuming I add package="lib.model" to the <database> tag). But then > the generated SQL file is lib.model.schema.sql. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
