Maybe better would be to store the id of the user not the username.
But the principle is right.
And this code of creating the query move to the JobTable class ..
create a method with userId parametter.
On 12 srp, 21:16, RusAlex <interpret...@gmail.com> wrote:
> I have my own opinion:
>
> I need to add new field "user" into job table, and use edited actions
> to show:
>
> class jobActions extends sfActions
> {
> public function executeIndex(sfWebRequest $request)
> {
> $this->jobs = Doctrine::getTable('JobeetJob')
> ->createQuery('a')
> ->where('a.user = ?' , $this->getUser()->getUsername())
> ->execute();
> }
>
> Is this a right approach for solving my task ?
--
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 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
