Well, no one likes to tag onto a 'whining' post. I shouldn't be surprised :-)
When I'm rich, (because of using symfony), I will hire somebody to produce 'database mentality' documentation. (See Postgres docs, or Oracle docs) On Nov 12, 8:40 pm, Dennis <gear...@sbcglobal.net> wrote: > I have had nothing but grief when it comes to using forms in Symfony. > I find that if I build a page using a form for one table, well of > course that works. But any time that I want more than one table's > information to go to or from a user, and with validation/file upload/ > widgets, LOTS of extra coding is needed in several places and it seems > inconsistent with each different approach I've seen on the web. > > ONE way that I've heard of a successful company doing it without > having to fight the minimal documentation and side effects with > embedding/merging is DON'T do either. Use a custom sfForm with hand > built validators and widgets. THEN use the ORM to save things. > > So the survey is do you do your forms with: > > A/ Only single table user displayed forms. > > B/ Using symfony embedding or merging functions. > > C/ Custom forms and handle parent child data in the Actions. > > D/ Use database views which symfony treats as just a table ( and you > get exactly > the form you want by specifying the view. (IS THIS POSSIBLE ;-) ? > > I'll give this 1-2 weeks 'out there', then I will summarize the > results in a post to this. -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@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=.
