To replicate this problem, use the following config...

config/doctrine/TestCountry.yml

TestCountry:
  tableName: test_country
  actAs:
    Timestampable:
      created:
        name: created_at
        type: timestamp
        format: Y-m-d H:i:s
        options:
          notnull: true
      updated:
        name: updated_at
        type: timestamp
        format: Y-m-d H:i:s
        options:
          notnull: true
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    name:
      type: string(2)
      fixed: true
      notnull: true

data/fixtures/TestCountry.yml:

TestCountry:
  country_1:
    name: gb

BTW, the error returned is as follows:

"validation error in class TestCountry?"

(In [5250]) [1.0, 1.1] Fixes issue with preInsert() and preUpdate() hooks being called after isValid() (fixes #1716)

The same error occurs if you have additional timestamp fields:

TestCountry:
  tableName: test_country
  actAs:
    Timestampable: ~
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    name:
      type: string(2)
      fixed: true
      notnull: true
   testtime:
      type: timestamp

Works for me with the following in the 1.0 sandbox:

Turned on validation:

Doctrine_Manager::getInstance()->setAttribute('validate', 'all');

Schema

TestCountry:
  tableName: test_country
  actAs:
    Timestampable:
      created:
        name: created_at
        type: timestamp
        format: Y-m-d H:i:s
        options:
          notnull: true
      updated:
        name: updated_at
        type: timestamp
        format: Y-m-d H:i:s
        options:
          notnull: true
  columns:
    id:
      type: integer
      primary: true
      autoincrement: true
    name:
      type: string(2)
      fixed: true
      notnull: true
    testtime:
      type: timestamp

Fixtures

TestCountry:
  country_1:
    name: gb
    testtime: '2008-09-01'

And run the following command:

./doctrine build-all-reload

What kind of database you're using? MySQL for example understand unix timestamps whereas PostgreSQL don't.

It would be interesting how the generated query looks like.

In my opinion the "Timestampable" timestamp fields will be filled with e.g. 2008-07-07 whereas the "normal" timestamp column will filled with an unix timestamp (seconds from 1970 etc).

The generated query inserts the formatted date, not a unix timestamp. You need to make sure in your data fixtures that the date value is wrapped in single quotes as well.

Ok, thank you.