1 / 8

Models in Symfony

Dive into the world of Symfony and Doctrine with this comprehensive guide by Sayed Ahmed, an experienced software engineer. This resource covers essential topics like querying data, debugging SQL, customizing object serialization, and utilizing configuration files in Symfony applications. Learn how to effectively fetch all data from a table, apply conditions to your queries, and manage results efficiently. Enhance your development skills with refactoring techniques and dynamic fixtures that ensure clean, maintainable code structures. Ideal for developers seeking to elevate their Symfony expertise.

mahsa
Télécharger la présentation

Models in Symfony

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Models in Symfony Sayed Ahmed B.Sc. Eng. in Computer Science & Engineering M. Sc. in Computer Science Exploring Computing for 14+ years sayed@justetc.net http://sayed.justetc.net

  2. The Doctrine Query Object • Get all data from a table • $this->jobeet_jobs = Doctrine::getTable('JobeetJob') ->createQuery('a') ->execute(); • Get data based on conditions • $q = Doctrine_Query::create() ->from('JobeetJob j') ->where('j.created_at > ?', date('Y-m-d H:i:s', time() - 86400 * 30));

  3. Debugging Doctrine generated SQL • You can see the complete SQLs as generated by Symfony in the /log directories • Such as frontend_dev.log • Doctrine generates prepared statements • The use of prepared statements dramatically reduces • your exposure to SQL injectionattacks • You can also check the SQL statements • using Symfonyweb debug toolbar

  4. Object Serialization • When you need to do something automatically • before a Doctrine object is serialized to the database • you can override the save() method of the model class • isNew() method • returns true • when the object has not been serialized yet • public function save(Doctrine_Connection $conn = null) { • if ($this->isNew() && !$this->getExpiresAt()) { • $now = $this->getCreatedAt() ? $this->getDateTimeObject('created_at')->format('U') : time(); $this->setExpiresAt(date('Y-m-d H:i:s', $now + 86400 * 30)); • } • return parent::save($conn); • }

  5. Custom Configuration • The Symfonyframework provides • a built-in configuration file for application specific settings • the app.yml file. • This YAML file can contain any setting you want: • Example File • # apps/frontend/config/app.yml • all: • active_days: 30 • From the application, the config variables can be retrieved as follows • sfConfig::get('app_active_days')

  6. Refactoring • The logic needs to be moved to model • The controller just needs to maintain the flow • Example • $this->jobeet_jobs = Doctrine_Core::getTable('JobeetJob')->getActiveJobs();

  7. Limit the Results • $q = Doctrine_Query::create() ->from('JobeetJob j') ->where('j.category_id = ?', $this->getId()) ->limit($max);

  8. Dynamic Fixtures • YAML files in Symfonycan contain • PHP code that will be evaluated just before the parsing of the file • The YAML parser won't like you • if you mess up with Indentation. • Keep in mind the following simple tips when adding PHP code to a YAML file: • The <?php ?> statements must always start the line or be embedded in a value • If a <?php ?> statement ends a line, you need to explicitly output a new line ("\n")

More Related