class NewsletterForm extends BaseNewsletterForm
{
  public function configure()
  {
    $this->widgetSchema['file'] = new sfWidgetFormInputFileEditable(array(
      'file_src' => '/uploads/'.$this->getObject()->getfile(),
      'is_image'  => true,
      'edit_mode' => !$this->isNew(),
      //'template'  => '<div>%file%<br />%input%<br />%delete% %delete_label%</div>',
    ));
 
    $this->validatorSchema['file'] = new sfValidatorFile(array(
      'required' => false,
      'path' => sfConfig::get('sf_upload_dir')
    ));
 
    $this->validatorSchema['file_delete'] = new sfValidatorPass();
  }
}

If you want to override the file name generated for your uploaded file, add a ‘generateXXXFileName()’ method to your model’s class where XXX is the column name that contains the file name (in this example, our column is “file”, so the method name is ‘generateFileFilename’. It takes a single parameter, which is an instance of sfValidatedFile.

class Newsletter extends BaseNewsletter
{
  public function generateFileFileName($file)
  {
    return $file->getOriginalName();
  }
}

>> doctrine Could not create database for c...o use near '-sb-test' at line 1

Turns out the issue is with the “-” in my test database name. Replacing the hyphens with underscores fixed the problem.

To use an example off of the doctrine-user group, imagine you have a Content object and this may or may not have a related Metadata record.

If you are familiar with Propel, then if you had your hydrated $content object, you could do

// with propel:
if ($metadata = $content->getMetadata()) {
  // do something with the related $metadata
}

and getMetadata() would return NULL if there was no related record to be found.

Doctrine will automatically create an empty related object if you request one, so calling $content->Metadata or $content['Metadata'] or $content->getMetadata() will always return a Metadata object, even if it does not exist in the database. So, you can’t rely on the same trick above to see if a related object exists.

So, how do you check if a related object actually exists? The first way, and my favorite, is using the exists() method to check if the related object is persistent (i.e. the object is saved in the DB).

// with doctrine 
if ($content->Metadata->exists()) { 
  // related metadata exists for this $content object
}

Using isset() will check if the related object has been hydrated/ loaded, but it will not do a query against the database to see if it exists there. So, if you fetch a Content object and do not do any joins in your query to join the related Metadata objects, then isset(), either by doing isset($business->Metadata) or $business->isset('Metadata') will *always* return false.

If your foreign key to the related object exists in your parent record (if content has a metadata_id field) you can always check the value of $content['metadata_id']. This will not work if the foreign key exists only in your metadata table (metadata has a column content_id, but content does not have a metadata_id column).

I think if you really wanted to do it right, if you expect to be checking for the existence of a related object (“Metadata”) on your collection of core objects (“Content”), you should do a join in your query so you don’t have to hit the database for every single Content record fetched to see if a related Metadata record exists.

Here are a few threads on this subject in the doctrine-user group:

• Call $record->Related without creating new object
• hasOne relationship
• Awkward handling of One-to-Zero-or-One relationships in Doctrine