Thanx for your reply. So how about creating patition manually, I mean for example I split a very large user table `my_users` to 100 tables called `my_users_00`, `my_users_01`, ... `my_users_99`, the last 2 number of the user_id decide which table it would belong to. I can easily define them in schema.yml with some simple php, but as you already expected, that the `build-all` task generate 100 model class file (also form, filter ...) which I would like to expect just 1 in there. I may write a class which can auto decide to use which model from the user_id, but i don't think it is good enough. Is there a better way to do these kind of stuff in symfony??
On May 24, 8:00 pm, "Ian P. Christian" <poo...@pookey.co.uk> wrote: > 2009/5/24 chrisyue <blizzch...@gmail.com> > > > I am a newbie in symfony, recently I am studying symfony by the jobeet > > tutorials, but I am used to creating partitioning for large table to > > improve performance. wish somebody would help me with this question, > > thx a lot. > > No ORM I know can do this. > I'd suggest creating an SQL script you can run to ALTER the tables as > required. > > -- > Blog:http://pookey.co.uk/blog > Follow me on twitter:http://twitter.com/ipchristian --~--~---------~--~----~------------~-------~--~----~ 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 symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
