I have thought about putting all routes etc in a single set of large
tables. The thing is, transit data comes from agencies in large chunks
representing transit service within a period of time. So, every couple
months or so, all of the data is switched out and new information is
imported for the next period of time. I figure it's just easier to do
it with separate tables, but perhaps you are right.
Thanks for your suggestions, Hristo. I've experimented with the
__construct method. In theory, it would work perfectly, except that
doctrine specifies the table name in a different type of notation,
before the class is defined - like this:
/**
* @ORM\Table(name=$this->agency_id . "_routes")
*/
class Route
{
public function __construct($agency_id) {
$this->agency_id = $agency_id;
}
//getters and setters, etc
}
Similarly, I'm not too sure how a factory method could solve that
problem, because the Table name definition is not actually within the
php code...
--
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
