I haven't followed the last discussions about sf 2.0 features, but
recently something come to my mind for sf 1.4 and maybe in 2.0 would
be even easyer.
Many times I have to use the same table structure for different
contents (but due to requests using different tables). That's a bit
boring cause it's the very same structure repeated.
Then I was wandering a way to define a key or something to the bundle
so it would work as a prefix to the table and other access of it.
In a sf 1.4 example:
contents:
columns:
cat_id: integer
title: string(50)
body: string(50)
categories:
columns:
title: string(50)
then set the prefixes 'foo' and 'bar' giving me the classes
FooContents, FooCategories, BarContents and BarCategories.
That's just a sugestion that, IMHO, may be usefull.
Thanks for this great framework, God bless
Sid
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" 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-devs?hl=en
To unsubscribe from this group, send email to
symfony-devs+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
