class ArticlePeer...
{
   static protected $STATUS_INTEGERS = array('open', 'closed');
   static protected $STATUS_VALUES = null;
 
   static public function getStatusFromIndex($index)
   {
     return self::$STATUS_INTEGERS[$index];
   }
 
   static public function getStatusFromValue($value)
   {
     if (!self::$STATUS_VALUES)
     {
       self::STATUS_VALUES = array_flip(self::$STATUS_INTEGERS);
     }
 
     $values = strtolower($value);
 
     if (!isset(self::STATUS_VALUES[$value])
     {
       throw new PropelException(sprintf('Status cannot take "%s" as a value', $value));
     }
 
     return self::STATUS_VALUES[strtolower($value)];
   }
}

class Article
{
   public function setStatusName($value)
   {
     $this->setStatus(ArticlePeer::getStatusFromValue($value));
   }
 
   public function getStatusName()
   {
     return ArticlePeer::getStatusFromIndex($this->getStatus());
   }
}

Comments on this snippet

#1 Luciano Andrade on 2006-11-21 at 04:30

In ArticlePeer.php: self::STATUS_VALUES shuld say self::$STATUS_VALUES self::STATUS_INTEGER shuld say self::$STATUS_INTEGER

and the variable values of the method getStatusFromValue is never used.

the if need and extra ) at the en of the line

In Article.php if you don't want to add a new field (StatusName) you could <pre> class Article { public function setStatus($value) { paret::setStatus(ArticlePeer::getStatusFromValue($value)); }

public function getStatus() { return ArticlePeer::getStatusFromIndex($this->getStatus()); } }

</pre>

#2 Satya Prakash on 2007-12-20 at 12:44

i did as said in this article. Now i want to use it.

i am trying to use it in admin/backend. I am trying to add dropdown list for this field instead of input field. This generator.yml is not giving any error: generator: class: sfPropelAdminGenerator param: model_class: Category theme: default

fields:
  category:       { name: Category }
  status_name:    { name: Status, type: select_tag }
 
list:
  fields:
    title:        { name: Title }
    status_name:       { name: Status, type: select_tag}
 
edit:
  display:
    "Create/Edit Category":         [category, status]
  fields:
    status_name:    { name: Status, type: select_tag}
 

Module is right.

#3 yousef nabulsi on 2007-12-29 at 02:57

This is a nice solution but the enum vales must be not be retrieved as fixed values (ie suppose i want to add or remove an enum value in future ), How could i do that without modifying the php code later .

#4 Chris Prior on 2008-01-11 at 11:57

@yousef: Use a 1:n table in the schema then. Like document_type for the base table document with document.document_type_id

#5 juan martin on 2008-05-29 at 08:45

I have one failed in line 18 of ArticlePeer.php

Warning: Illegal offset type in /srv/www/libros/lib/model/LibrosPeer.php on line 18

My generator.yml is =>

edit: fields: status: { name: Status, type: select_tag, params: peer_method=getStatusFromIndex related_class=Libros }

I need help is urgent i have proyect wednesday 4 - jun -2008

Thanks

#6 André Lademann on 2009-03-04 at 11:32

By using the Admin Generator the simplest way is to use an _partical.

generator.yml

edit: display: MemberTyp: [ _typ ]

_typ.php

<?=select_tag('member[typ]', options_for_select(array('band' => 'Band', 'location' => 'Location'), $selected =$member->getTyp()));?>

The "selected"-option I use to select the current choice from database.

I hope it help! André Lademann

#7 Peter Kaminski on 2009-09-14 at 06:35

Consider that it may be just as good to use a varchar field instead of emulating an enum with an int. Depending on your data, the database performance may be similar, and the symfony code to implement it with a varchar field is easy and clean -- you can just add sfWidgetFormChoice() and sfValidatorChoice() in the object's form class, and that automatically gets used in the frontend and backend forms.

Fabien has a great example here, where he explains how to "convert the status widget to a choice":

http://www.symfony-project.org/blog/2008/10/14/new-in-symfony-1-2-make-your-choice

The Jobeet tutorial has a similar solution for job type, see "we want its value to be restricted to a list of choices: full time, part time, or freelance":

http://www.symfony-project.org/blog/2008/12/10/jobeet-day-10-the-forms

As for database performance, there are a number of articles on the web comparing (real) enum vs. varchar vs. int, etc. for this use. Here is one:

http://www.mysqlperformanceblog.com/2008/01/24/enum-fields-vs-varchar-vs-int-joined-table-what-is-faster/

Pete

#8 Massimiliano Arione on 2009-09-18 at 04:20

in your schema.yml:

status: { type: varchar, sqltype: enum, size: "'open','close'" }

KISS! ;-)