Thanks for your reply! I implemented everything so far and it seems to work. I also clear only the autoloading config file and not the whole cache. Thanks for this hint. Dynamically generating of some model classes will not occure so often at the producation server, so there should not be so much performance issues, but i will keep an eye on it.
- Frank Am 10.05.2007 um 13:58 schrieb Luciano A. Andrade: > > I think that the only bad thing could be clear the cache, you could > clear the config_autoload.yml.php only (i think that's the only one > you need), you may need to keep an eye on the load of the server. > > On 5/10/07, Frank Stelzer <[EMAIL PROTECTED]> wrote: >> >> Hi everybody, >> i have to add dynamically tables to my existing model. I use >> doctrine as >> ORM and create for every new "dynamically" model a new schema file. >> >> Afterwards i would run the doctrine_build_model task in an action, >> so that >> the model classes from this new table are generated (maybe >> additional the >> clear-cache task too). >> >> My question is now, if it is a good way to run this task on an >> producation >> server or if one should not do this at all. >> >> The whole model is very small in the beginning , only few tables will >> exist, so that these tasks will not run very long. But i really do >> not >> know, if it is a good thing, what i am doing :) >> >> - Frank >> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
