ZC40 – Doctrine Relations and Data Fixtures

Jon Lebensold · 2009-12-09 01:23:25

This episode of zendcasts will cover how we can write Data Fixtures and extend our data model to include a simple one-to-many using Doctrine's schema.yml file. I also noticed in the code of my last example that Model loading wasn't working properly. I cover the fix in the video, however I'd like to highlight it here too. In your _initDoctrine() method, make sure you load the models:
Doctrine::loadModels($doctrineConfig['models_path]);

also, I'd like to extend a welcome to the folks at ServerGrove Networks for sponsoring this episode of Zendcasts. ServerGrove specializes in Zend Framework hosting and they've offered a 10% rebate on hosting with coupon code "zc". If you're looking for a host, be sure to check them out.

Bugger · 2009-12-09 18:27:00

at 18:31 in the video it looks liek you have a typo "DOctrine::"

Fordnox · 2009-12-09 22:28:32

Thanks for another great Episode.
I saw you write static functions in your model. I honestly do not know, but will that not be a problem later with a unit tests ?
Is static method behaving the same as object->method call in PhpUnit ?
Just want to make sure, it would be very interesting to hear your answer

Jon Lebensold · 2009-12-10 14:44:03

static methods are fine when you're trying to encapsulate a concept inside a method. They cause problems when people use them to assignment of objects, however I'm using them for one-time invocation. When I write the public static methods in the model, I'm treating the model as a flat interface. If queries are becoming increasingly complex, it might be worth looking at "Aggregate Roots" and the Repository pattern, however these patterns add additional layers which might be unnecessary.

Fordnox · 2009-12-12 15:53:45

Thanks, that confirms my understanding that static functions are not always the right solution then things go complex.

Jon Lebensold wrote:

static methods are fine when you're trying to encapsulate a concept inside a method. They cause problems when people use them to assignment of objects, however I'm using them for one-time invocation. When I write the public static methods in the model, I'm treating the model as a flat interface. If queries are becoming increasingly complex, it might be worth looking at "Aggregate Roots" and the Repository pattern, however these patterns add additional layers which might be unnecessary.

Michiel Thalen · 2010-01-21 03:34:00

How do you use functions (like NOW()) in the fixture?
And do you know why my timestamp field ends up being a datetime field in the database?

ryan.horn · 2010-01-21 15:14:35

Data fixtures are meant to be static. The whole point is that you have your application data at a "fixed" state and can thus properly test to ensure that any logic which interacts with the data is working properly. So instead of using NOW() in your fixture, you would use what NOW() might output at any given point in time (which is in datetime format for mysql).

Ex: 2010-01-21 10:01:49

Also, timestamp is a data type internal to doctrine. The actual column type that is generated when doctrine creates your tables depends on the database driver being used. For most (including mysql), this is a column type of "datetime", which is a combination of the date and time (based on the IS0-8601 standard for formatting). See http://www.doctrine-project.org/documen … :timestamp

udo · 2010-01-27 11:47:45

For building the db you are using this schema:

options:
  type: INNODB
  collate: utf8_general_ci
  charset: utf8
  
User:
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    name: string(300)
    email: string(300)
    phone: string(9)
    car_id: integer
  relations:
    Car:
      local: car_id
      foreign: id

Car:
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    brand: string(300)
  relations:
    Users:
      class: User
      foreign: car_id
      local: id
      type: many

An alternative is using the "detect_relations" option. The schema.yml file looks like this:

options:
  type: INNODB
  collate: utf8_general_ci
  charset: utf8
detect_relations: true  
  
User:
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    name: string(300)
    email: string(300)
    phone: string(9)
    car_id: integer

Car:
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    brand: string(300)

iiTyr · 2010-03-27 10:57:27

Hi, i've been following Zendcasts for a while now, but only just registered, and i don't think i've seen this anywhere yet,

I know this might be an old topic, but this should be worth mentioning,

I don't think i am the only one who designs his/her databases with MySQL Workbench( http://wb.mysql.com/ ), and now i've recently picked up a very usefull workbench- plugin to use with doctrine.

This plugin allows you to export your database models to a yaml file for use with doctrine.

It should be noted that i havn't tested this yet with a live application, but the exported yaml files look promising.

(EDIT: it seems to be working, although i had a few issue's with accidently calling a field in a table 'order' which screwed up the generated sql)

the plugin can be found at: http://code.google.com/p/mysql-workbenc … ne-plugin/

Last edited by iiTyr (2010-03-27 13:30:06)

tawfekov · 2010-03-27 13:54:29

Hi iiTyr ,
Really thanks for your suggestion , its really nice idea and will ease the YAML Generation .
btw in the doctrine cli interface there are many helpful commands for reverse engineering like :

doctrine generate-models-db
doctrine generate-models-yaml
doctrine generate-sql
doctrine generate-yaml-db
doctrine generate-yaml-models

and Thanks for sharing us with this plugin
I look forward to hear form you and others as well

iznogood · 2010-03-28 03:41:00

iiTyr wrote:

I don't think i am the only one who designs his/her databases with MySQL Workbench( http://wb.mysql.com/ ), and now i've recently picked up a very usefull workbench- plugin to use with doctrine.

Wow! All these years and I had never taught to look for something other then phpmyadmin and custom mysql scripts. Thanks for making me discover this tool!!

@bobie · 2010-05-12 04:20:07

Fordnox wrote:

Thanks for another great Episode.
I saw you write static functions in your model. I honestly do not know, but will that not be a problem later with a unit tests ?
Is static method behaving the same as object->method call in PhpUnit ?
Just want to make sure, it would be very interesting to hear your answer

I totally agree with you. These tutorials here are very helpful and informative. It helps me with my class in IT and in my research. I hope you will post more tutorials here. Thanks and keep it up.

Zendcasts Forum

#1 2009-12-09 01:23:25

ZC40 – Doctrine Relations and Data Fixtures

#2 2009-12-09 18:27:00

Re: ZC40 – Doctrine Relations and Data Fixtures

#3 2009-12-09 22:28:32

Re: ZC40 – Doctrine Relations and Data Fixtures

#4 2009-12-10 14:44:03

Re: ZC40 – Doctrine Relations and Data Fixtures

#5 2009-12-12 15:53:45

Re: ZC40 – Doctrine Relations and Data Fixtures

#6 2010-01-21 03:34:00

Re: ZC40 – Doctrine Relations and Data Fixtures

#7 2010-01-21 15:14:35

Re: ZC40 – Doctrine Relations and Data Fixtures

#8 2010-01-27 11:47:45

Re: ZC40 – Doctrine Relations and Data Fixtures

#9 2010-03-27 10:57:27

Re: ZC40 – Doctrine Relations and Data Fixtures

#10 2010-03-27 13:54:29

Re: ZC40 – Doctrine Relations and Data Fixtures

#11 2010-03-28 03:41:00

Re: ZC40 – Doctrine Relations and Data Fixtures

#12 2010-05-12 04:20:07

Re: ZC40 – Doctrine Relations and Data Fixtures

Board footer