Doctrine Project

[DC-313] Ordering m2m relationship with column from related table (with orderBy option)

Fri, 18 Feb 2011 03:32:42 +0000

I find no way to define automatic orderBy in m2m relations with column not from reference table, but actual related table.

E.g. BlogPost <= m2m through BlogPostCategory => BlogCategory
I need BlogPost->Categories ordered by BlogCategory.name

class BlogPost extends Doctrine_Record
{
    public function setTableDefinition()
    {
        $this->hasColumn('title', 'string', 128);
        $this->hasColumn('content', 'string');
    }
    
    public function setUp()
    {
        $this->hasMany('BlogCategory as BlogCategories', array('local' => 'id_blog_post', 'foreign' => 'id_blog_category', 'refClass' => 'BlogPostCategory', 'orderBy' => 'name'));        
    }
}

class BlogCategory extends Doctrine_Record
{
    public function setTableDefinition()
    {
        $this->hasColumn('name', 'string', 128);
    }
    
    public function setUp()
    {
        $this->hasMany('BlogPost as BlogPosts', array('local' => 'id_blog_category', 'foreign' => 'id_blog_post', 'refClass' => 'BlogPostCategory'));
    }
}

class BlogPostCategory extends Doctrine_Record
{
    public function setTableDefinition()
    {
        $this->hasColumn('id_blog_post', 'integer', null, array('primary' => true));
        $this->hasColumn('id_blog_category', 'integer', null, array('primary' => true));
    }
    
    public function setUp()
    {
        $this->hasOne('BlogPost', array('local' => 'id_blog_post', 'foreign' => 'id', 'onDelete' => 'CASCADE'));
        $this->hasOne('BlogCategory', array('local' => 'id_blog_category', 'foreign' => 'id', 'onDelete' => 'CASCADE'));
    }
}

The resulting query contains doubled 'name' column in ORDER BY clause, both from reference table and related table, e.g. ORDER BY t2.name, t3.name

I tried putting the following code in BlogCategory::setTableDefinition() instead of attribute in relation definition in BlogPost record:

$this->option('orderBy', 'name');

but the result was the same.

Maybe I'm doing something wrong? Is there a possibility to define an alias, where to get column name from - in orderBy attribute?

Thanks in advance.

[DC-627] Work on link-table and leftJoin

Tue, 13 Apr 2010 05:07:32 +0000

Looking at the attachment to see the little schema.
Tree table : items, items_children and children.

The link-table items_children is here to create a many-to-many relationships between Items and Children.

So, after configure the YAML and generated Models.
We can do something like that :

$query = Doctrine_Query::create ()
->select ("items.title, children.title")
->from ("Item items")
->leftJoin ("item.children children");
$items = $query->execute ();

$items //An array of items
$items[0]->title //A string
$items[0]->children //An array of children

The SQL Output of the query is :

SELECT `i`.`id_item` AS `i_id_item`, `i`.`title` AS `ititle`, `c`.`id_child` AS `cid_child`, `c`.`title` AS `c_title` FROM `items` `i` LEFT JOIN `items_children` `i2` ON (`i`.`id_item` = `i2`.`id_item`) LEFT JOIN `children` `c` ON `i2`.`id_child` = `c`.`id_child`

All array are order by something, in this case it's a natural order which come from the items_children order into database.

Now, I want to apply a condition, or a filter on the items_children table.
If I translate my demand to SQL Query :

SELECT `i`.`id_item` AS `i_id_item`, `i`.`title` AS `ititle`, `c`.`id_child` AS `cid_child`, `c`.`title` AS `c_title` FROM `items` `i` LEFT JOIN `items_children` `i2` ON (`i`.`id_item` = `i2`.`id_item`) LEFT JOIN `children` `c` ON `i2`.`id_child` = `c`.`id_child` ORDER BY `c1`.`index`

Or something crazy :

SELECT `i`.`id_item` AS `i_id_item`, `i`.`title` AS `ititle`, `c`.`id_child` AS `cid_child`, `c`.`title` AS `c_title` FROM `items` `i` LEFT JOIN `items_children` `i2` ON (`i`.`id_item` = `i2`.`id_item`) LEFT JOIN `children` `c` ON `i2`.`id_child` = `c`.`id_child` WHERE `c1`.`index` > 2

But how can I do that with DQL ? Because I have no access to the Link-table.

Link-Table are use to create many-to-many, that could be OOP array. So we have to be allowed to add "index" to order the result. Also, we have to be allowed to add condition on this tables, like "datePromote" or simply "enabled".

The solution should be on the following DQL Query :

$query = Doctrine_Query::create ()
->select ("items.title, children.title")
->from ("Item items")
->leftJoin ("item.children children")
->leftJoin ("ItemsChildren link_table")
->orderBy ("link_table.index")
$items = $query->execute ();

But the SQL Output is :

SELECT `i`.`id_item` AS `i_id_item`, `i`.`title` AS `ititle`, `c`.`id_child` AS `cid_child`, `c`.`title` AS `c_title` FROM `items` `i` LEFT JOIN `items_children` `i2` ON (`i`.`id_item` = `i2`.`id_item`) LEFT JOIN `children` `c` ON `i2`.`id_child` = `c`.`id_child`, `items_children` `i3` ORDER BY `i3`.`index`

To conclude, it's a blocker problem. Because I can't use a standard DB schema.

Regards,
Armetiz.

[DC-665] Named parameters doesn't work on MSSQL anymore

Wed, 22 Sep 2010 00:55:15 +0000

After upgrading to Doctrine 1.2.2 queries with named arguments doesn't work anymore.
Whenever querying like
$query = Doctrine_Query::create();
$customer = $query->from('Customers')
->where("id = :id"
, array('id'=>$user['customer_id']))
->fetchOne(array(), Doctrine::HYDRATE_ARRAY);

I get the error
SQLSTATE[HY000]: General error: 10007 Incorrect syntax near ':'. [10007] (severity 5)

If changing the query to
$query = Doctrine_Query::create();
$customer = $query->from('Customers')
->where("id = ?"
, array($user['customer_id']))
->fetchOne(array(), Doctrine::HYDRATE_ARRAY);
it works fine.
Testing with MySQL works fine, so it seems contained to MSSQL

[DC-701] Aggregates functions do not return proper values when using many relationships and limits

Mon, 1 Nov 2010 20:12:17 +0000

Hi All

I have encountered a problem that seems very core to the way that doctrine works – if you apply an aggregate function to a column in a table and then join to another table via a many relationship while also using a limit, like so:

$q = Doctrine_Query::create();
$q->from('Customer Customer'); 
$q->addSelect('COUNT(Customer.id) as COUNT_customer_id');
$q->addSelect('Customer_Order.id as order_id'); 
$q->leftJoin('Customer.Order Customer_Order'); // Many relationship here
$q->limit(20);

It produces this correct DQL:

SELECT COUNT(Customer.id) as COUNT_customer_id, Customer_Order.id as order_id 
FROM Customer Customer 
  LEFT JOIN Customer.Order Customer_Order 
LIMIT 20

However the SQL it produces will not return an accurate count – the count is restricted by the limit:

SELECT COUNT(p.id) AS p__0, p2.id AS p2__1 
FROM product_customers p 
  LEFT JOIN product_orders p2 ON p.id = p2.customer_id 
WHERE p.id IN ('1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20')

This produces a count of 21 instead of what it should be (1000).

The reason for this is because Doctrine's internal functionality does an intermediary query where it gets gets the ids needed from the customer table in order to use them as the IN portion of the constraints on the final query – like so:

SELECT DISTINCT p3.id FROM product_customers p3 LIMIT 20

It may seem strange that I am applying a limit to a query which will aggregate to 1 to row . In the actual queries that alerted me to this problem I am using a group by. The reason I am not reporting this bug with a group by in my example however is that you can not use a group by with a many relationship and a limit in doctrine 1.2.2 as it works currently (see bug: ~~DC-594~~). However I am personally able to use a limit with a group by and many relationship since I am using a version of the code I patched my self to repair bug ~~DC-594~~.

Here is my sample schema in case its helpful.

detect_relations: false
package: Example
options:
  type: INNODB
  charset: utf8
Order:
  tableName: orders
  columns:
    order_id:
      type: integer(4)
      primary: true
      notnull: true
    customer_id:
      type: integer(4)
    order_date: timestamp
  relations:
    Customer:
      type: one
      local: customer_id
      foreign: customer_id
  options:
    type: InnoDB
Customer:
  tableName: customers
  columns:
    customer_id:
      type: integer(4)
      primary: true
      notnull: true
      autoincrement: true
    firstname:
      type: string(45)
    lastname:
      type: string(45)
    streetaddress:
      type: string(45)
    city:
      type: string(45)
    state:
      type: string(45)
    postalcode:
      type: string(45)
  relations:
    Order:
      type: many
      local: customer_id
      foreign: customer_id
  options:
    type: InnoDB

Thanks much.

Will Ferrer

_{edit: split SQL code to make the discussion readable without huge horizontal scrolling...}

[DC-770] Result Cache

Tue, 29 Jun 2010 05:50:36 +0000

Doctrine result cache isn't working properly.

Here a simple example, when I'm calling query->execute (); parentProgram is related to a video.
Into the Doctrine_Query_Abstract.php file

line 1014 : I have just add some code to output data.
[code]
if ($cached === false)

{ // cache miss $stmt = $this->_execute($params); $this->_hydrator->setQueryComponents($this->_queryComponents); $result = $this->_hydrator->hydrateResultSet($stmt, $this->_tableAliasMap); $oVideo = $result[0]; echo "not cached "; var_dump (count ($oVideo->parentProgram->getReferences ())); $cached = $this->getCachedForm($result); $cacheDriver->save($hash, $cached, $this->getResultCacheLifeSpan()); }

else

{ $result = $this->_constructQueryFromCache($cached); $oVideo = $result[0]; echo "cached "; var_dump (count ($oVideo->parentProgram->getReferences ())); exit (0); }

[/code]

The output of a query execution (the first with an empty APC cache) with "useResultCache" is :

not cached int(1)
cached int(0)

The problem is coming from the serialize php function that can't serialize protected properties..
getReferences is a getter to a protected property.. So data result can't work properly.

A solution could be use __sleep function, and a public property that contain all important protected data.

[DC-791] [PostgreSQL] In case model is build from existing database sequence name is invalid and doctrine throw exception

Wed, 25 Aug 2010 02:40:04 +0000

Firstly I created database directly in postgresql.
After that I generated schema from existsing database and after all i built model.

When I try to insert new record to database I received following error:

sequence "Category_id_seq" does not exist

In schema file sequence name is defined like this: sequence: '"Address_id_seq"'
There's are apostrophes and quotes.

In Category model file is same like above, apostrophes and quotes.

When I remove quotes from sequence in model files everything is ok and there're no problems with insert new row to database.

[DC-839] Version classes not built for models using package attribute

Tue, 8 Mar 2011 11:06:47 +0000

For models using the 'package' attribute in the schema definition, the version classes do not get created. However, the version table gets created.

There is no problem during the build, but when loading fixtures, there is a fatal error: Class TaxCodeVersion not found

TaxCode:
package: Masters
tableName: Fin_Tax_Codes
actAs:
Activateable: ~
SoftDelete: ~

Versionable:
tableName: fin_tax_codes_version
1. versionColumn: version
className: %CLASS%Version
1. auditLog: true
  Auditable: ~
  Timestampable: ~
  .......

[DC-860] 0 down vote favorite In some circumstances Doctrine_Core::getTable('%Name%') returns Doctrine_Table instance instead of %Name%Table one.

Mon, 6 Sep 2010 12:13:35 +0000

In some circumstances Doctrine_Core::getTable('%Name%') returns Doctrine_Table instance instead of %Name%Table one.
So custom %Name%Table's methods become unavailable.

In order to give a demonstration of this improper behavior : here is a schema of small issue tracking system

User:
actAs: [Timestampable]
tableName: issue_user
columns:
user_id:

{ type: integer, primary: true, autoincrement: true }

user_name:

{ type: string(255) }

user_role:

{ type: enum, values: [worker, dispatcher, manager] }

managed_by:

{ type: integer }

password:

{ type: string(32) }

salt:

{ type: string(32) }

relations:
Manager:
foreignAlias: Workers
class: User
local: managed_by
foreign: user_id
type: one
foreignType: many

Issue:
actAs: [Timestampable]
columns:
issue_id:

{ type: integer, primary: true, autoincrement: true }

from_ceh:

{ type: string(255) }

from_name:

{ type: string(255) }

from_phone:

{ type: string(255) }

from_location:

{ type: string(255) }

comp_name:

{ type: string(255) }

comp_serial:

{ type: string(255) }

comp_os:

{ type: enum, values: [Win95, Win98, WinNT, WinME, Win2000, WinXP, Vista, Win7] }

issue_title:

{ type: string(255) }

comment:

{ type: string(255) }

owner_id:

{ type: integer }

is_executed:

{ type: bool }

relations:
Owner:
onDelete: CASCADE
foreignAlias: Issues
class: User
local: owner_id
foreign: user_id
type: one
foreignType: many

When I just call Doctrine_Core::getTable('User') it returns UserTable instance, but if I call it after such a query:

Doctrine_Query::create()
->select('u.user_id, ws.user_id, i.*')
->from('User u, u.Workers ws, ws.Issues i')
->where('u.user_id=', $manager_id)
->fetchArray();

calling Doctrine_Core::getTable('User') returns Doctrine_Table instance

[DC-918] Causing ORA-01791 when try to sort on relation field and use limit in query to Oracle DB

Sat, 6 Nov 2010 08:48:17 +0000

Schema in yml format
in Symfony it looks more simple, but i'm going to show relation in detail

PrType:
  columns:   
    name:                   { type: string(255), notnull: true }                          

PrTypeTranslation:
  columns:   
    id:                     { type: integer, notnull: true }
    name:                   { type: string(255), notnull: true }
    lang:                   { type: string(255), notnull: true }
  relations:
    PrType:                 { onDelete: CASCADE, local: id_id, foreign: id, foreignAlias: Translation }

When i try to execute this code:

   $q = Doctrine_Query::create()
            ->from('PrType tp')
            ->leftJoin('tp.Translation t WITH t.lang = ?', 'ru')
            ->orderBy('t.name')
            ->limit(10);

doctrine executes next statement:

SELECT "p"."id", "p2"."name" AS "p2__name", "p2"."lang" AS "p2__lang"
FROM "pr_type" "p"
LEFT JOIN "pr_type_translation" "p2" ON "p"."id" = "p2"."id" AND ("p2"."lang" = :oci_b_var_1)
WHERE "p"."id" IN (
              SELECT a."id" FROM ( 
                          SELECT DISTINCT "p3"."id"
                          FROM "pr_type" "p3"
                          INNER JOIN "pr_type_translation" "p4" ON "p3"."id" = "p4"."id" AND ("p4"."lang" = 'ru') 
                          ORDER BY "p4"."name" ) a 
                          WHERE ROWNUM <= 10) 
ORDER BY "p2"."name"

This sql code produces next error

ORA-01791: not a SELECTed expression

Error occures, because (from ORACODE)

There is an incorrect ORDER BY item. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands are constants or SELECT list expressions

[DC-926] Doctrine ignored PORTABILITY_FIX_CASE and ATTR_FIELD_CASE settings when building query

Fri, 12 Nov 2010 17:29:13 +0000

Setting:
$conn->setAttribute(Doctrine_Core::ATTR_PORTABILITY, Doctrine_Core::PORTABILITY_FIX_CASE)
$conn->setAttribute(Doctrine_Core::ATTR_FIELD_CASE, CASE_UPPER)

I expect column names in built queries to be uppercase, but they remain to be lowercase.

[DC-952] Non-Equal Nest Relations Not Working - from "Children" side

Thu, 24 Mar 2011 04:59:10 +0000

I've copy & pasted example from http://www.doctrine-project.org/projects/orm/1.2/docs/manual/defining-models/1_0#relationships:join-table-associations:self-referencing-nest-relations:non-equal-nest-relations .
I've created User backend module using doctrine:generate-admin backend User task. On how to reproduce the error:

1. Add 3 User objects (A,B,C)
2. Open generated edit form for User A.
3. Set User B as Children from Children list and Save
4. Set User B and C as Chidren from Children list and Save

As a result you will see only C set as Children, and strange situation in database :

UserReference Table:

parent_id | child_id
pk_B | pk_B (!!!)
pk_A | pk_C

[DC-962] Broken logic when doctrine translates limit's into subqueries, with joins. (with patch)

Wed, 2 Feb 2011 10:19:59 +0000

Problem exists when Doctrine formulates a subquery to perform a limit when a join in included.

The problem is that the where clause that doctrine creates for the subquery (the WHERE IN clause) is inserted as the first where clause.
This will break the parameter duplicate done at Doctrine_Query_Abstract:969, as the order of the parameters is now wrong.

Consider:

 
select * from table
join metadata WITH c = ?
where a = ? and b = ?
limit 1

with parameters be (1, 2, 3)

Doctrine will translate this to

 
select * from table
join metadata WITH c = ?
where table.id IN (
    select id from table
    join metadata WITH c = ?
    where a = ? and b = ?
    limit 1
)
and a = ? and b = ?

Doctrine will duplicate the params (Doctrine_Query_Abstract:969) to (1, 2, 3, 1, 2, 3), but now they are in the wrong order completely.
They should be (1,1,2,3,2,3).

The easy fix is to move the limit subquery to the LAST where clause, which would reuslt in a query like so:

 
select * from table
join metadata WITH c = ?
where a = ? and b = ?
and table.id IN (
    select id from table
    join metadata WITH c = ?
    where a = ? and b = ?
    limit 1
)

Attached is a patch to fix this issue, along with a patch that fixes all unit tests referring to the old query format.

[DC-972] MySQL field aliases with triple ticks

Wed, 16 Feb 2011 11:14:24 +0000

In revision 7691 something has happened. Ever since I updated my Doctrine to that revision all my queries having " ... fieldname AS aliasname ... " go crazy and make the PHP to throw an exception, like this:

'Doctrine_Connection_Mysql_Exception' with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 't.`id`' in 'field list'. Failing Query:
"SELECT `t`.`id` AS `t_id`, `t`.```id``` AS `t0`, `t`.```name``` AS `t1`, `t`.`id` AS `t0`, `t`.`name` AS `t_1` FROM `territoryCombined` `t` ORDER BY `t`.`name` asc"'
in ...path here.../doctrine/lib/Doctrine/Connection.php:1082

The problem is that the DQL parser somewhere along the process encapsualtes aliases in ticks, but then it does it again in lib/Doctrine/Formatter.php : quoteIdentifier() , which is called in lib/Doctrine/Connection : quoteIdentifier() , which is called in lib/Doctrine/Query.php : processPendingFields() @ between lines 485 and 512. The problem is that by the time the alias name gets to line 507 it is already encapsualted in ticks, but it does it again. At the end we end up with ```alias``` , which is not good.

It only happens to aliases. If I say select('*') or select("t.id, t.name") then it executes properly. Only the aliases couse problems.

A test query:

$vTerritories = Doctrine_Query::create()
->select("t.id as territory_id, t.name as territory_name")
->from('TerritoryCombined t')
->orderBy('t.name asc')
->fetchArray();

MY PROPOSED PATCH:

If I change the Formatter::quoteIdentifier() to this:

public function quoteIdentifier($str, $checkOption = true)

{ $tmp = $this->conn->identifier_quoting; // I move up this line to here because I need it if ( (substr($str, 0, 1) == $tmp['start']) && (substr($str, -1) == $tmp['end']) ) return $str; // new line; is it already quoted? if yes, then don't do it again // the rest is unchanged }

then it works correctly. Please note I only tested that in MySQL, as we use MySQL in all our projects.

[DC-1021] i am executing doctrine type query i am geting error please gave me reply

Sun, 24 Jul 2011 15:05:33 +0000

$query = new Doctrine_Query();
$query->select('e.entity_name,e.entity_id,s.id,s.parent_id,e.ffc_entity_id,c.country_id,c.country_name')
//$query->select('e.entity_name,e.entity_id,s.id,s.parent_id,e.ffc_entity_id,ea.Country')
->from('Entities e')
->leftJoin('e.EntityAddresses ea ON ea.entity_id = e.entity_id AND ea.address_type ="M"')
->leftJoin('ea.Country c ON ea.country = c.country_id')
->leftJoin('e.ActiveFactories s')
->where('e.status=1');
if(!empty($alpha))
{
$query->andWhere("e.entity_name like '".$alpha."%'");
}
$query->andWhere("s.company_id=".$parentId)
->andWhere("e.entity_type=2")
->andWhere('s.status=1')
->groupBy('e.entity_id');

[DC-1025] Doctrine is unable to handle table names with spaces

Tue, 2 Aug 2011 10:37:03 +0000

When trying to query a table which contains spaces I get the following exception

I have attached an simple example to reproduce

C:\Documents and Settings\daniel\Dokumenter\NetBeansProjects\test>php doctrineTest.php

Fatal error: Uncaught exception 'Doctrine_Query_Exception' with message 'Unknown table alias with' in C:\Doctrine-1.2.3\Doctrine\Query\Abstract.php:856
Stack trace:
#0 C:\Doctrine-1.2.3\Doctrine\Query.php(1022): Doctrine_Query_Abstract->getComponentAlias('with')
#1 C:\Doctrine-1.2.3\Doctrine\Query.php(1239): Doctrine_Query->_buildSqlFromPart()
#2 C:\Doctrine-1.2.3\Doctrine\Query.php(1133): Doctrine_Query->buildSqlQuery(true)
#3 C:\Doctrine-1.2.3\Doctrine\Query\Abstract.php(958): Doctrine_Query->getSqlQuery(Array)
#4 C:\Doctrine-1.2.3\Doctrine\Query\Abstract.php(1026): Doctrine_Query_Abstract->_execute(Array)
#5 C:\Documents and Settings\daniel\Dokumenter\NetBeansProjects\test\doctrineTest.php(18): Doctrine_Query_Abstract->execute()
#6

{main}

thrown in C:\Doctrine-1.2.3\Doctrine\Query\Abstract.php on line 856

[DC-1031] CLONE -Multiple connections and i18n (raised as unresolved - original ticket marked as resolved)

Wed, 28 Mar 2012 08:20:53 +0000

I used to work with a single database named "doctrine". The query was working properly.

I then decided to use 2 databases so I got my schema like this:

connection: doctrine

Category:
actAs:
I18n:
actAs:
Sluggable:
fields: [name]
Timestampable: ~
fields: [name, description]
columns:
id: ~
name:
type: string(255)
notnull: true
description: string

User:
connection: second
columns:
id: ~
name:
type: string(255)
notnull: true

I did setup my connections in config/databases.yml this way:

all:
doctrine:
// ....
second:
// ....

build-model, build-forms, build-filters and cc got ran. But now, I got an exception saying the "Translation" relation doesn't exist. The Base Models include correctly the bindComponent line:

Doctrine_Manager::getInstance()->bindComponent('Category', 'doctrine');

For now, I managed to kind of fixing it with simply swapping the databases order in my config/databases.yml and it's now working again perfectly.

I forgot to mention that in the CategoryTable when i call $this->getConnection()->getName(), it outputs "second"

[DC-1034] ORA-00904 in Doctrine_Connection_Oracle

Thu, 1 Sep 2011 08:43:20 +0000

When i execute this code:

 
$q = Doctrine_Query::create()
            ->from('AGENT ag')
            ->leftJoin('ag.CHANTIER_AGENT cag)
            ->orderBy('ag.nom')
            ->limit(10)
            ->offset(10)
            ->execute();

Doctrine executes :

 
SELECT a.pk AS a__pk, a.ts AS a__ts, a.ck_agent AS a__ck_agent, a.matricule AS a__matricule, a.nom AS a__nom, a.prenom AS a__prenom, a.agent_maitrise AS a__agent_maitrise, 
c.pk AS c__pk, c.ts AS c__ts, c.ck_chantier_agent AS c__ck_chantier_agent, c.ek_chantier AS c__ek_chantier, c.fk_chantier AS c__fk_chantier, c.ek_agent AS c__ek_agent, c.fk_agent AS c__fk_agent 
FROM AGENT a 
LEFT JOIN CHANTIER_AGENT c ON a.ck_agent = c.ek_agent 
WHERE a.ck_agent IN 
(SELECT b.ck_agent 
FROM ( SELECT a.*, ROWNUM AS doctrine_rownum 
FROM ( SELECT DISTINCT a2.ck_agent, a2.nom FROM AGENT a2 LEFT JOIN CHANTIER_AGENT c2 ON a2.ck_agent = c2.ek_agent ORDER BY a2.nom ) 
a2 ) 
b 
WHERE doctrine_rownum BETWEEN 11 AND 20) 
ORDER BY a.nom

The problem is in function _createLimitSubquery in Doctrine_Connection_Oracle :

 
                    $query= 'SELECT '.$this->quoteIdentifier('b').'.'.$column.' FROM ( '.
                                 'SELECT '.$this->quoteIdentifier('a').'.*, ROWNUM AS doctrine_rownum FROM ( '
                                   . $query . ' ) ' . $this->quoteIdentifier('a') . ' '.
                              ' ) ' . $this->quoteIdentifier('b') . ' '.
                              'WHERE doctrine_rownum BETWEEN ' . $min .  ' AND ' . $max;

Error occures, because table name is AGENT and Doctrine give the first letter of the table name for identifier.
To correct this. Use more than one letter in the quoteIdentifier.

 
                    $query = 'SELECT '.$this->quoteIdentifier('limb').'.'.$column.' FROM ( '.
                                 'SELECT '.$this->quoteIdentifier('lima').'.*, ROWNUM AS doctrine_rownum FROM ( '
                                   . $query . ' ) ' . $this->quoteIdentifier('lima') . ' '.
                              ' ) ' . $this->quoteIdentifier('limb') . ' '.
                              'WHERE doctrine_rownum BETWEEN ' . $min .  ' AND ' . $max;

[DC-1035] ORA-01791 due to bad driver name in Doctrine_Adapter_Oracle

Thu, 1 Sep 2011 09:31:24 +0000

When i execute this code:

 
$q = Doctrine_Query::create()
            ->from('AGENT ag')
            ->leftJoin('ag.CHANTIER_AGENT cag)
            ->orderBy('ag.nom')
            ->limit(10)
            ->execute();
$q2 = Doctrine_Query::create()
            ->from('AGENT ag')
            ->leftJoin('ag.CHANTIER_AGENT cag)
            ->orderBy('ag.nom')
            ->limit(10)
            ->execute();

Doctrine executes :

 
SELECT a.pk AS a__pk, a.ts AS a__ts, a.ck_agent AS a__ck_agent, a.matricule AS a__matricule, a.nom AS a__nom, 
a.prenom AS a__prenom, a.agent_maitrise AS a__agent_maitrise, c.pk AS c__pk, c.ts AS c__ts, c.ck_chantier_agent AS c__ck_chantier_agent, 
c.ek_chantier AS c__ek_chantier, c.fk_chantier AS c__fk_chantier, c.ek_agent AS c__ek_agent, c.fk_agent AS c__fk_agent 
FROM AGENT a 
LEFT JOIN CHANTIER_AGENT c ON a.ck_agent = c.ek_agent 
WHERE a.ck_agent IN (
SELECT a2.ck_agent FROM ( 
SELECT DISTINCT a2.ck_agent, a2.nom FROM AGENT a2 LEFT JOIN CHANTIER_AGENT c2 ON a2.ck_agent = c2.ek_agent ORDER BY a2.nom ) 
a2 WHERE ROWNUM <= 10) ORDER BY a.nom

SELECT a.pk AS a__pk, a.ts AS a__ts, a.ck_agent AS a__ck_agent, a.matricule AS a__matricule, a.nom AS a__nom, 
a.prenom AS a__prenom, a.agent_maitrise AS a__agent_maitrise, c.pk AS c__pk, c.ts AS c__ts, c.ck_chantier_agent AS c__ck_chantier_agent, 
c.ek_chantier AS c__ek_chantier, c.fk_chantier AS c__fk_chantier, c.ek_agent AS c__ek_agent, c.fk_agent AS c__fk_agent 
FROM AGENT a 
LEFT JOIN CHANTIER_AGENT c ON a.ck_agent = c.ek_agent 
WHERE a.ck_agent IN (
SELECT a2.ck_agent FROM ( 
SELECT DISTINCT a2.ck_agent FROM AGENT a2 LEFT JOIN CHANTIER_AGENT c2 ON a2.ck_agent = c2.ek_agent ORDER BY a2.nom ) 
a2 WHERE ROWNUM <= 10) ORDER BY a.nom

This causes "Oracle DB Error ORA-01791 not a SELECTed expression" because the sql query don't have a2.nom in SELECT DISTINCT and it's indispensable for ORDER BY a2.nom
The problem is caused by the variable $attributes in Doctrine_Adapter_Oracle :

 
protected $attributes = array(Doctrine_Core::ATTR_DRIVER_NAME    => "oci8",
                                  Doctrine_Core::ATTR_ERRMODE        => Doctrine_Core::ERRMODE_SILENT);

The problem is in Query.php line 1417 :

	if ($driverName == 'pgsql' || $driverName == 'oracle' || $driverName == 'oci' || $driverName == 'mssql' || $driverName == 'odbc') {

The driver name declared in Doctrine_Adapter_Oracle not in this conditional.
To resolve this we have to modify the declaration of $attributes in Doctrine_Adapter_Oracle to :

protected $attributes = array(Doctrine_Core::ATTR_DRIVER_NAME    => "oracle",
                                  Doctrine_Core::ATTR_ERRMODE        => Doctrine_Core::ERRMODE_SILENT);

An other problem is probably located at line 1409

 if (($driverName == 'oracle' || $driverName == 'oci') && $this->_isOrderedByJoinedColumn()) {

and 1497

        if (($driverName == 'oracle' || $driverName == 'oci') && $this->_isOrderedByJoinedColumn()) {

if don't correct the declaration of $attributes in Doctrine_Adapter_Oracle.

[DC-1040] allow queries with table joins across different databases

Thu, 17 Nov 2011 14:42:03 +0000

I'm currently working on a project which relies upon several databases declared in databases.yml in symfony 1.4.8.

I was facing an issue that has already been raised by other people, namely that you can't join tables which reference each other among different mysql databases.

I've dug a bit in the Doctrine_Query class and came to a solution that is acceptable for us, and allows now to make joins accross databases. Description follows :

first change is in the Doctrine_Core class, that gets stuffed with a new constant :
const ATTR_DATABASE_NAME = 0x1DB;

this constant allows us to add a new attribute to the databases.yml file as in :
gesdoc:
class: sfDoctrineDatabase
param:
dsn: mysql:host=127.0.0.1;dbname=gesdoc
username: root
password:
attributes:

************* NEW ATTRIBUTE BELOW ************
database_name: gesdoc
default_table_collate: utf8_general_ci
default_table_charset: utf8

after that, a few changes have been done in the Doctrine_Query class which is attached to this issue for the sake of readability.

This may not be optimal, and probably need some regression testing, but it is currently working fine on our test server.

after this is done, I was able to issue queries like the following :
$x = DocumentTable::getInstance()->createQuery('d')
->distinct()
->leftJoin('d.Travail t')
->leftJoin('t.CdcIndInt ci')
->leftJoin('ci.CdcIndExt ce')
->leftJoin('ce.Cahierdescharge cdc')
->where('cdc.cdc_chro = ?', $cdc_chro)
->addWhere('d.id != ?', $document_id)
->execute();

where the referenced tables are in different databases. The necessary object binding has been done in every model class following the paradigm :

Doctrine_Manager::getInstance()->bindComponent('CdcIndInt ', 'gescdc');
abstract class BaseCdcIndInt extends sfDoctrineRecord
{
...
}

I don't know if this description is clear enough, so let me know if something is missing/wrong.

[DC-347] AddPendingJoinConditions doesn't work if alias equals model name

Fri, 29 Jan 2010 06:50:10 +0000

If the alias in a from-query is equal to the model name, I get an exception when executing the query after adding a "pendingJoinCondition".

See attached testCase.

[DC-371] Lazy loading - doctrine makes extra queries into db

Thu, 23 Dec 2010 20:22:10 +0000

Just downloaded symfony 1.4

First of all I have a query:

$q = \Doctrine_Query::create()
->select('u., ur.')
->from('UserDb u')
->leftJoin('u.RealUserDetailsDb ur')
->leftJoin('u.MockUserDetailsDb um')
->where('u.id = :user_id')
;
$user = $q->fetchOne(array(':user_id' => $uid));

After that I'm accessing the fields of this object:

$userArray = array(
'id' => $this->getUser()->getId(),
'real_user_details_id' => $this->getUser()->getRealUserDetailsId(),
'mock_user_details_id' => $this->getUser()->getMockUserDetailsId(),
'real_user_details' => array(),
'mock_user_details' => array()
);

This is the actual queries into DB:

NR1:
SELECT u.id AS u_id, u.user_real_id AS uuser_real_id, u.user_mock_id AS uuser_mock_id, u2.id AS u2id, u2.nickname AS u2nickname, u2.email AS u2_email FROM user u LEFT JOIN user_real u2 ON u.user_real_id = u2.id LEFT JOIN user_mock u3 ON u.user_mock_id = u3.id WHERE (u.id = :user_id)

NR2:
SELECT u.id AS u_id, u.user_real_id AS uuser_real_id, u.user_mock_id AS u_user_mock_id FROM user u WHERE (u.id = '1') LIMIT 1

As you can see there are TWO queries however there should be only one query. The problem is that u.user_real_id is NULL in database and when I do 'real_user_details_id' => $this->getUser()->getRealUserDetailsId() doctrine does not have enough intelligence to understand that these fields have been already requested in NR1. If I comment this field, everything works well.

SURPRISE!
And now a surprise... if I modify a little bit my first query: "~~>select('u.')" instead of , "~~>select('u., ur.*')" it WON'T make TWO queries. It will make ONLY ONE!

As you understand this a very critical bug and of course our system won't go to production with this bug.

P.S. Is it possible to turn off the lazy loading in doctrine?

[DC-489] Doctrine_Record seems to have a bug with default values when updating

Thu, 20 Jan 2011 08:53:02 +0000

So lets see the table:

User:
tableName: users
columns:
id:
type: integer(1)
fixed: false
unsigned: true
primary: true
autoincrement: true
username:
type: string(32)
fixed: false
unsigned: false
primary: false
notnull: true
autoincrement: false
password:
type: string(48)
fixed: false
unsigned: false
primary: false
notnull: true
autoincrement: false
role:
type: enum
fixed: false
unsigned: false
values:

admin
support
default: support <----- Unable to render embedded object: File (ROOT OF EVIL) not found.
primary: false
notnull: true
autoincrement: false

So lets say we have a user with `role` = 'support' and want to set em
'admin' we wrote

$user = new App_Model_User();
$user->assignIdentifier(1);
$user->role = 'admin';
$user->save();
var_dump($user->toArray());

in debugger we see SQL query been made:

[0.55 ms] UPDATE users SET role = ? WHERE id = ?

bindings: admin
1

array(6)

{ ["id"]=> int(1) ["display_name"]=> string(13) "Administrator" ["username"]=> string(4) "root" ["password"]=> string(40) "45bb0f589525a2f0f2a48620bb59b1b8baef0c1d" ["role"]=> string(5) "admin" ["is_active"]=> bool(true) }

Superb! Works as it should! So lets now set role of this user back to
'support':

$user = new App_Model_User();
$user->assignIdentifier(1);
$user->role = 'support'; // This value defined as default in scheme,
thats why have problems
$user->save();
var_dump($user->toArray());

in debugger we didnot see any UPDATE queries! However object is been
changed, results just has not been flushed to database.

array(6)

I cant overcome this problem right now, unfortunatelly (well I can
just remove all default values from table definitions or use
Doctrine_Query for updating staff.. but I'd like to use models

However if I use Doctrine_Query of even

$user = Doctrine_Core::getTable('App_Model_User')->find(1);

instead of

$user = new App_Model_User();
$user->assignIdentifier(1);

updates works well...

[DC-515] HYDRATE_RECORD_HIERARCHY broken with many roots

Wed, 9 Jun 2010 03:11:58 +0000

DB schema:

Category:
actAs:
NestedSet:
hasManyRoots: true
rootColumnName: root_id
columns:
id:
type: integer(4)
primary: true
autoincrement: true
name:
type: string(64)
notnull: true
image: string(64)
indexes:
tree:
fields: [lft, rgt, root_id]

Sample data:

id: '1'
name: 'Przykładowa kategoria 1'
image: null
root_id: '1'
lft: '1'
rgt: '6'
level: '0'

id: '2'
name: 'Przykładowa kategoria 2'
image: null
root_id: '2'
lft: '1'
rgt: '6'
level: '0'
-
id: '3'
name: 'Przykładowa podkategoria 1'
image: null
root_id: '2'
lft: '2'
rgt: '5'
level: '1'
-
id: '4'
name: 'Przykładowa podkategoria 2'
image: null
root_id: '2'
lft: '3'
rgt: '4'
level: '2'
-
id: '5'
name: teset1
image: null
root_id: '1'
lft: '2'
rgt: '5'
level: '1'
-
id: '6'
name: test2
image: null
root_id: '1'
lft: '3'
rgt: '4'
level: '2'

When using HYDRATE_RECORD_HIERARCHY, the first top-level category is empty. Everything is assigned to the other one. Only single-root trees work properly.

[DC-586] Doctrine outputs invalid SQL when using Limit and Order By conditions in MSSQL

Thu, 18 Mar 2010 19:08:42 +0000

I have a Doctrine model which connects to a MSSQL database. I was trying to run the following query:

$q = Doctrine_Query::create()
    ->select('*')
    ->from('Comment c')
    ->innerJoin('c.RecordType')
    ->innerJoin('c.Department')
    ->limit(10)
    ->orderBy('c.Counter');

The code failed with a SQL Syntax exception so I took a look at the generated query and found the following (SELECT fields shortened for readabilty):

SELECT * FROM (
	SELECT TOP 10 * FROM (
		SELECT TOP 10 [c].[counter] AS [c__counter], [c].[loanid] AS [c__loanid]... ... ...
		FROM comments c
			INNER JOIN [SystemTypes] [s] ON [c].[recordtype] = [s].[code] AND [s].[fieldname] = 'RecordType'
			INNER JOIN [SystemTypes] [s2] ON [c].[department] = [s2].[code] AND [s2].[fieldname] = 'Department'
		ORDER BY [c].[counter]
	) AS [inner_tbl]
	ORDER BY [inner_tbl].[counter] AS [c__counter] DESC
) AS [outer_tbl]
ORDER BY [outer_tbl].[counter] AS [c__counter] ASC

As you can see, the ORDER BY clauses on the inner_tbl and outer_tbl segments have AS clauses which do not belong there. If you fix the ORDER BY statements the query runs just fine.

So I decided to prod around the Mssql.php connection class and found the following:

140 public function modifyLimitQuery($query, $limit = false, $offset = false, $isManip = false, $isSubQuery = false)
141 {
...
169                    $field_array = explode(',', $fields_string);
170                    $field_array = array_shift($field_array);
171                    $aux2 = preg_split('/ as /', $field_array);
172                    $aux2 = explode('.', end($aux2));
173
174                    $aliases[$i] = trim(end($aux2));
...
232 }

Line 171 seems to be in charge of setting up the orderBy aliases but it is looking for a lower case ' as ' string which doesn't exist in this SQL expression. Changing that to a case insensitive regular expression search seems to fix the problem:

171                    $aux2 = preg_split('/ as /i', $field_array);

Here is the resulting SQL with the change:

SELECT * FROM (
	SELECT TOP 10 * FROM (
		SELECT TOP 10 [c].[counter] AS [c__counter], [c].[loanid] AS [c__loanid]... ... ...
		FROM comments c
			INNER JOIN [SystemTypes] [s] ON [c].[recordtype] = [s].[code] AND [s].[fieldname] = 'RecordType'
			INNER JOIN [SystemTypes] [s2] ON [c].[department] = [s2].[code] AND [s2].[fieldname] = 'Department'
		ORDER BY [c].[counter]
	) AS [inner_tbl]
	ORDER BY [inner_tbl].[c__counter] DESC
) AS [outer_tbl]
ORDER BY [outer_tbl].[c__counter] ASC]

This seems to fix the problem but I don't know if it'll create a regression. It's a start though. Anyone have any thoughts on this?

[DC-644] _getCacheKeys() exhausts memory

Wed, 6 Jul 2011 08:17:14 +0000

My scripts have excessive memory consumption and I've often saw in my logs:

PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2097152 bytes) in /proj/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Cache/Apc.php on line 111

Looking into the code I've found which function to blame:

protected function _getCacheKeys()
{
$ci = apc_cache_info('user');
$keys = array();

foreach ($ci['cache_list'] as $entry)

Unknown macro: { $keys[] = $entry['info']; ######### THIS IS THE LINE }

return $keys;
}

My server extensively uses APC caching and it's normal to have many cache keys.
Obviously retrieving ALL of them is time and memory consuming.
As I'm not well versed with Doctrine's code, I didn't want to dive further in.

Is there another way to avoid this pitfall?

[DC-659] Sluggable behavior does not check uniqueness on insert if a slug is manually set, causing SQL error/crash

Tue, 5 Oct 2010 11:14:25 +0000

The Sluggable behavior has the following code:

Sluggable.php

    /**
     * Set the slug value automatically when a record is inserted
     *
     * @param Doctrine_Event $event
     * @return void
     */
    public function preInsert(Doctrine_Event $event)
    {
        $record = $event->getInvoker();
        $name = $record->getTable()->getFieldName($this->_options['name']);

        if ( ! $record->$name) {
            $record->$name = $this->buildSlugFromFields($record);
        }
    }

However, this can lead to problems...

If the user incorrectly assigns a duplicate slug to the record then there is no uniqueness checking in doctrine and you get an uncaught SQL error looking something like this:

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'my-slug-en_GB' for key 'foo_i18n_sluggable_idx'

If this kind of "don't do a preInsert check if I manunally set the slug" behavior is a FEATURE then it would be best to have an option to allow it to be disabled. If it is a BUG then I would suggest that the preInsert method should be changed to:

Sluggable.php

    /**
     * Set the slug value automatically when a record is inserted
     *
     * @param Doctrine_Event $event
     * @return void
     */
    public function preInsert(Doctrine_Event $event)
    {
        $record = $event->getInvoker();
        $name = $record->getTable()->getFieldName($this->_options['name']);

        if ( ! $record->$name) {
            $record->$name = $this->buildSlugFromFields($record);
        } else { // Still check for slug uniqueness when you insert
            $record->$name = $this->buildSlugFromSlugField($record);
        }
    }

[DC-674] NULL Dates are translated to '0000-00-00' after upgrading to 1.2.2

Wed, 6 Oct 2010 06:29:40 +0000

Once the upgrade was done from Doctrine 1.2.1 to 1.2.2 we discovered that date related issues started to appear.
With dates that are persisted in DB as NULL are translated to "0000-00-00" when retrieved from DB. This has occurred in multiple places and is quite worrying as there is a lot of dates in our project. This means that everywhere in our codebase where we check a datevalue in our Models is NULL we need also to check for the string literal "0000-00-00".

[DC-690] Wrong data type for oracle integer

Tue, 8 Jun 2010 11:05:38 +0000

Trying to migrate from doctrine 1 to 1.2 and this problem came up to me, i cant map a column to integer(7) (which should create a number(7) column) using Oracle, he always create a NUMBER(20) field.

Taking a look at Doctrine_DataDict_Oracle i realize the problem is here.

[DC-725] Call record->get('RelationManyToManyName', FALSE) corrupt the record and generate a exception when calling record->save()

Wed, 9 Jun 2010 07:55:21 +0000

Imagine a simple case. Contact can have many categories.
Doing thoses calls:

$c = Doctrine::getTable('Contact')->findOneById($id);
$c->get('Categories', false);
$c->save();

Generate the following error

PHP Fatal error:  Call to a member function save() on a non-object in /lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Connection/UnitOfWork.php on line 443
PHP Stack trace:
PHP   1. {main}() /test/doctrine/get_with_no_load_corrupt_many_to_many_assoc_.php:0
PHP   2. Doctrine_Record->save() /test/doctrine/get_with_no_load_corrupt_many_to_many_assoc_.php:51
PHP   3. Doctrine_Connection_UnitOfWork->saveGraph() /lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Record.php:1705
PHP   4. Doctrine_Connection_UnitOfWork->saveAssociations() /lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Connection/UnitOfWork.php:137

[DC-735] Imported objects not converted to objects and parsed as string when a setter method exists

Fri, 22 Jul 2011 05:09:34 +0000

If you set a setter method for a model which is for a relation the data import no longer works. This seems to be because in the _processRow method it checks if a method exists and then passes the default value rather than checking whether a relation exists first and passing the imported object.

This effectively means you can't overload a setter method and still use the data import.

[DC-743] Incompatibilty between fixture import and accessors extends

Fri, 22 Jul 2011 02:28:49 +0000

Hello,

I had a problem when i try to import data with an extended accessors when i try to insert a content with a relation. I discovered this problem in symfony.

For example, here is my table :

 
News:
  tableName: ne_news
  columns:
    id:           { type: integer(4), primary: true, autoincrement: true }
    author_id:    { type: integer(4), notnull: true }
    name:         { type: string(255) }
    description:  { type: text }
  relations:
    author: { class: sfGuardUser, onDelete: NULL, local: author_id, foreign: id, foreignAlias: sfGuardUser }

And the fixture :

 
SfGuardUser:
  sadmin:
    username:       admin
    password:       admin
    is_super_admin: true
  author1:
    username: myname
    
News:
  News1:
    name: Test 1
    description: Description of news 1
    author: author1

I import it with symfony doctrine:data-load and it works.

If i add a news.class.php and extends the autogenerated class it fails.

 
    public function setAuthor($v)
    {
        //__log('extending setter');
        return $this->_set('author', $v);
    }

WhenDoctrine_Data_Import finds the setAuthor function, it wont transform author1 in object so $v will be a string, not an sfGuardUser object.

What do you think? Is a common behavior, how can i extends my accessor?

[DC-747] Sequence name of build process is different to the one used in UnitOfWorks (based on DC521 with updated TestCase)

Thu, 17 Jun 2010 06:47:38 +0000

I moved our project from doctrine 1.2.1 to 1.2.4. The build process stops because of this patch. We are using primary keys with an alias. It seems that the generation of the sequence name in the build-process is different to the one used in UnitOfWorks.

Example:

Authority:
columns:
a_id:

{ name: a_id as id, type: integer, primary: true, autoincrement: true }

name:

{ type: string }

This will generate a sequence called "authority_a_id", but it will try no "currval" the sequence "authority_id".

I'll try to provide a UnitTest. The current seems broken.

php -l Ticket/DC521TestCase.php
PHP Parse error: syntax error, unexpected $end, expecting T_FUNCTION in Ticket/DC521TestCase.php on line 143

Parse error: syntax error, unexpected $end, expecting T_FUNCTION in Ticket/DC521TestCase.php on line 143
Errors parsing Ticket/DC521TestCase.php

[DC-755] CLONE [DC-558] incorrect handling of MODEL_CLASS_PREFIX causes Doctrine_Migration_Diff to drop the whole database when working from YAML (Regression)

Sun, 10 Oct 2010 18:51:58 +0000

Replicating the bug:
1. Set ATTR_MODEL_CLASS_PREFIX non-null
2. create schema file with entity
3. run doctrine build-all
4. copy schema file
5. edit schema file to add column to entity
6. run generate-migrations-diff from copy of schema file to edited schema file

Expected (previous) behaviour:
Migration is generated to add the new column to entity

Real behaviour:
Drops entity from database and creates new

[DC-802] Alias in select and having

Sat, 7 Aug 2010 15:39:30 +0000

i have query

$q = Doctrine_Query::create()
->select('g.,gp.,st.,np.,v.,s.,max(gp.card_date) as md')
->from('gragdans as g')
->innerJoin('g.Pribs_ gp')
->leftJoin('gp.Streets_ st')
->leftJoin('gp.Viddocs_ v')
->leftJoin('gp.Sobits_ s')
->leftJoin('st.Npunkts_ np')
->where('g.grid in '.$idlst,1)
->orderby('fam')
->having('gp.card_date=md');

When it runs i have error:

<b>Fatal error</b>: Uncaught exception
'Doctrine_Connection_Mysql_Exception' with message 'SQLSTATE[42S22]:
Column not found: 1054 Unknown column 'md' in 'having clause'' in Z:
\home\new\www\system\application\plugins\doctrine\lib\Doctrine
\Connection.php:1082

SQL for it looks like:

SELECT g.grid AS g_grid, g.fam AS gfam, g.nam AS g_nam, g.otc AS
g_otc, g.date_rogd AS gdate_rogd, g.gosgrid AS g_gosgrid,
g.rogd_place AS g_rogd_place, g.pol AS g_pol, g.reg_date AS
g_reg_date, g.deesp AS gdeesp, p.pribid AS p_pribid, p.grid AS
p_grid, p.strid AS pstrid, p.hom AS phom, p.cor AS p_cor, p.kva
AS p_kva, p.reg_date AS preg_date, p.vidid AS p_vidid, p.pas_ser
AS p_pas_ser, p.pas_no AS ppas_no, p.org_name AS p_org_name,
p.pas_date AS p_pas_date, p.sobid AS p_sobid, p.reg_expire AS
p_reg_expire, p.card_date AS pcard_date, s.strid AS s_strid,
s.npid AS s_npid, s.name AS sname, v.vidid AS v_vidid, v.name AS
v_name, s2.sobid AS s2sobid, s2.cod_s AS s2_cod_s, s2.cod_oi AS
s2_cod_oi, s2.name AS s2name, n.npid AS nnpid, n.name AS n_name,
n.sid AS n_sid, MAX(p.card_date) AS p_0 FROM gragdans g INNER JOIN
prib p ON g.grid = p.grid LEFT JOIN streets s ON p.strid = s.strid
LEFT JOIN viddoc v ON p.vidid = v.vidid LEFT JOIN sobit s2 ON p.sobid
= s2.sobid LEFT JOIN npunkt n ON s.npid = n.npid WHERE (g.grid in (4,
13, 19, 20)) HAVING p.card_date=md ORDER BY g.fam

But i need Query looks like:

SELECT g.grid AS g_grid, g.fam AS gfam, g.nam AS g_nam, g.otc AS
g_otc, g.date_rogd AS gdate_rogd, g.gosgrid AS g_gosgrid,
g.rogd_place AS g_rogd_place, g.pol AS g_pol, g.reg_date AS
g_reg_date, g.deesp AS gdeesp, p.pribid AS p_pribid, p.grid AS
p_grid, p.strid AS pstrid, p.hom AS phom, p.cor AS p_cor, p.kva
AS p_kva, p.reg_date AS preg_date, p.vidid AS p_vidid, p.pas_ser
AS p_pas_ser, p.pas_no AS ppas_no, p.org_name AS p_org_name,
p.pas_date AS p_pas_date, p.sobid AS p_sobid, p.reg_expire AS
p_reg_expire, p.card_date AS pcard_date, s.strid AS s_strid,
s.npid AS s_npid, s.name AS sname, v.vidid AS v_vidid, v.name AS
v_name, s2.sobid AS s2sobid, s2.cod_s AS s2_cod_s, s2.cod_oi AS
s2_cod_oi, s2.name AS s2name, n.npid AS nnpid, n.name AS n_name,
n.sid AS n__sid, MAX(p.card_date) AS md FROM gragdans g INNER JOIN
prib p ON g.grid = p.grid LEFT JOIN streets s ON p.strid = s.strid
LEFT JOIN viddoc v ON p.vidid = v.vidid LEFT JOIN sobit s2 ON p.sobid
= s2.sobid LEFT JOIN npunkt n ON s.npid = n.npid WHERE (g.grid in (4,
13, 19, 20)) group by fam HAVING p.card_date=md

This query run fine and give me what i need.

Doctrine dont use 'md' alias instead it convert it to 'p__0'

[DC-815] Model's default sorting breaks subqueries

Mon, 14 Mar 2011 18:01:49 +0000

It works except subqueries. Main table's order is added to subquery and vice versa. SQL query looks like this:

{{
SELECT t.id AS t_id FROM ticket_d_c9999_record t WHERE (t.id = (SELECT MAX(t2.id) AS t20 FROM ticket_d_c9999__record t2 ORDER BY t.id ASC, t2.id ASC)) ORDER BY t.id ASC, t2.id ASC
}}

Query fails because there is >>no such column "t.id"<<.

I include a testcase when it is all visible.

BTW. there is nothing about that feature (and relation orderBy) in docs. It is only in UPGRADE file.

[DC-857] postHydrate not called for One to One relations, when ATTR_HYDRATE_OVERWRITE == false, and the record is cached in the table's identityMap

Sun, 5 Sep 2010 12:41:13 +0000

When objects are hydrated with a join to a one to one relation, if the queried object is stored in the table's cache, and ATTR_HYDRATE_OVERWRITE set to false, then the one to one relation's postHydrate method will never be called.

This is due to this line.

 
} else if ( ! isset($prev[$parent][$relationAlias])) {

...which will always evaluate to false, and postHydrate will ever be called, as the record has been pulled from the table cache here

[DC-922] master-slave replication with i18n behavior

Wed, 10 Nov 2010 02:34:37 +0000

I'm trying to use sfDoctrineMasterSlavePlugin for database replication with Symfony 1.4 and PHP 5.3. But facing problem while selecting I18n records and receiving "Unknown relation alias Translation" error.

I've also tried same with implementation solution given in master-slave chapter of doctrine cookbook but no success.

Is anyone facing same problem with sfDoctrineMasterSlavePlugin and i18n behavio? Is there any solution of the problem?

[DC-932] Queries fail when a model contains underscore and we try to apply a limit

Fri, 19 Nov 2010 08:47:27 +0000

Actually, I've a dead simple schema.yml, with two tables:

T_Media:
actAs:
Timestampable: ~
columns:
media_id:

{ type: integer, primary: true, autoincrement: true }

name: string(25)

J_Acl:
columns:
media_id: integer
relations:
Media:

{ class: T_Media, local: media_id, foreign: media_id, onDelete: CASCADE }

I have some fixtures:
T_Media:
m1:
name: foobar

J_Acl:
a1:
Media: m1

And then, the DQL query I want to execute:

"From T_Media m INNER JOIN m.J_Acl order by m.created_at limit 1"

But if I run this query, for instance in CLI, I got an error:
./symfony doctrine:dql "From T_Media m INNER JOIN m.J_Acl order by m.created_at limit 1"

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'test_noel.t2__media' doesn't exist.
Failing Query: "SELECT DISTINCT t2.media_id FROM t2_media t2 INNER JOIN j2_acl j2 ON t2.media_id = j2.media_id ORDER BY t2.created_at LIMIT 1"

Notes:

the query works if I do not apply the limit clause.
if I remove the underscore from the model, or if I set manually the tableName to remove the double underscore, it works

[DC-963] Doctrine cache - Salt dissociation

Mon, 18 Apr 2011 10:13:28 +0000

Doctrine Cache store data into a persistence storage.

Regarding APC, Doctrine use a share storage.
Doctrine is able to cache SQL from DQL, and DOM from SQL.
To do this, Doctrine create a DQL hash, and store the SQL result refer to the hash.

I'm using a server to host two Doctrine project, a preproduction & production Website. In some case, DQL is the same on both project, but the data model definition isn't.

Preproduction convert DQL to SQL using data model definition, and store the SQL result into APC cache refer to the DQL hash.
Production create a DQL hash, this is the same hash as preproduction.. So production instance use the SQL refer to the preproduction..

I'm not sure about the quality of this explanation... But I can add some information is needed.

The solution of this problem is easy. Just add a SALT to any cache id's. It's a Doctrine_Cache problem, not only a Doctrine_Cache_APC problem..
For Query cache it's not really important because this cache is optional, but for result cache.. It's more critical.
The SALT can be define when instantiate the Doctrine_Cache object, it's just an option..

$cacheDriver = new doctrine_Cache_Apc ();
$cacheDriver->setOption ("salt", "domain.tld");

[DC-978] Doctrine_Connection_Mssql dies on modifyLimitSubquery every time

Sun, 27 Feb 2011 17:17:16 +0000

Looking at the latest version of Doctrine_Connection_Mssql in git repo:
https://github.com/doctrine/doctrine1/blob/b4dc8e66a89a7e17cd195c489b18005e19ca9ea5/lib/Doctrine/Connection/Mssql.php

In Doctrine_Query:getLimitSubquery() there is a call to Doctrine_Connection_Mssql::modifyLimitSubquery().

public function modifyLimitSubquery(Doctrine_Table $rootTable, $query, $limit = false, $offset = false, $isManip = false)
{
	return $this->modifyLimitQuery($query, $limit, $offset, $isManip, true);
}

This in turn calls Doctrine_Connection_Mssql::modifyLimitQuery() wihtout passing the $queryOrigin parameter:

    public function modifyLimitQuery($query, $limit = false, $offset = false, $isManip = false, $isSubQuery = false, Doctrine_Query $queryOrigin = null)
    {
        if ($limit === false || !($limit > 0)) {
            return $query;
        }

        $orderby = stristr($query, 'ORDER BY');

        if ($offset !== false && $orderby === false) {
            throw new Doctrine_Connection_Exception("OFFSET cannot be used in MSSQL without ORDER BY due to emulation reasons.");
        }
        
        $count = intval($limit);
        $offset = intval($offset);

        if ($offset < 0) {
            throw new Doctrine_Connection_Exception("LIMIT argument offset=$offset is not valid");
        }

        $orderbySql = $queryOrigin->getSqlQueryPart('orderby');
        $orderbyDql = $queryOrigin->getDqlPart('orderby');

        if ($orderby !== false) {
            $orders = $this->parseOrderBy(implode(', ', $queryOrigin->getDqlPart('orderby')));

            for ($i = 0; $i < count($orders); $i++) {
...

From just looking at the above code, the query chokes on the first call to a $queryOrigin method. It seems like there is a lot of missing code here which should work with the $query directly when $queryOrigin is not available...

What is the point of $orderbySql and $orderbyDql variables when they are not used anywhere?

This code looks like it's half way done and untested.

[DC-980] Moving all ALTERS queries to the end of generated sql file (task build-sql)

Fri, 4 Mar 2011 06:42:03 +0000

Actual in case of using multi database configuration and foreign keys between them.

Now build-sql task generates SQL query for database by database in alphabetical order. It's ugly when we have multidatabase configuration and foreign keys between their tables. It's impossible to do 'import-sql' without errors beucase foreign keys constrains to nonexisting tables are in next database in order.

I have added some code to strings 1176-...

[DC-1007] Cannot update a field to NULL with MSSQL connection

Wed, 25 May 2011 19:43:52 +0000

When trying to update a field to NULL in a MSSQL database, Doctrine generates the following request:

    UPDATE table SET fieldThatMustBeNull = , anotherField = 'blabla';

therefore generating a syntax error.

A fix would be to override the update method in the Doctrine_Connection_Mssql and add the following behavior:

Doctrine_Connection_Mssql

    public function update(Doctrine_Table $table, array $fields, array $identifier)
    {
        if (empty($fields)) {
            return false;
        }

        $set = array();
        foreach ($fields as $fieldName => $value) {
            if ($value instanceof Doctrine_Expression) {
                $set[] = $this->quoteIdentifier($table->getColumnName($fieldName)) . ' = ' . $value->getSql();
                unset($fields[$fieldName]);
            } else if (is_null($value)) {
                $set[] = $this->quoteIdentifier($table->getColumnName($fieldName)) . ' = NULL';
                unset($fields[$fieldName]);
            } else {
                $set[] = $this->quoteIdentifier($table->getColumnName($fieldName)) . ' = ?';
            }
        }

        $params = array_merge(array_values($fields), array_values($identifier));

        $sql  = 'UPDATE ' . $this->quoteIdentifier($table->getTableName())
              . ' SET ' . implode(', ', $set)
              . ' WHERE ' . implode(' = ? AND ', $this->quoteMultipleIdentifier($table->getIdentifierColumnNames()))
              . ' = ?';

        return $this->exec($sql, $params);
    }

[DC-1009] save() also updates fields which should not be

Wed, 8 Jun 2011 15:40:42 +0000

When I want to do a simple update like this :

$batches = ExamResultsBatchTable::getInstance()->retrieveByExamBatchStatus(ExamResultsBatch::valid_status_code);
foreach($batches as $batch)
{
$batch->setExamBatchStatusId($batchStatusId);
$batch->setStatusDate(date('Y-m-d'));
$batch->save();
}
Only exam_batch_status_id and status_date should be updated (see screenshot before), but columns exam_batch_status_id ,status_date AND exam_subject_id are updated,with the same value (23) (screenshot after_with_save).

If I run this:
$toto = Doctrine_Query::create()
->update('ExamResultsBatch erb')
->set('erb.exam_batch_status_id', 23)
->set('erb.status_date', date('Y-m-d'))
~~>where('erb.id = ?' , $batch~~>getId())
->execute();
Everything is correctly done.

here is the simpliest case.

The same problems are signaled on other tables in the database, but different tables can be impacted by one save() (the execute() query still works fine).

Example : 2 foreign tables will be updated , even if the save() action should only concern the main table, and one field (which is not a foreign key).
The corresponding foreign key fields in the 2 foreign tables, will be updated with the value given (here 23).

Because save() is used in a lot of different places in our app, I need to find a solution to fix save(), or if not possible to override it to run a execute()like query.

Thanks for your help.
Don't hesitate to ask if you want more details.

Yan

[DC-1050] Doctrine_Relation_ForeignKey ignores ATTR_COLL_KEY attribute

Wed, 7 Mar 2012 13:02:40 +0000

Doctrine_Relation_ForeignKey::fetchRelatedFor() executes the following code at line 70:

$coll = $this->getTable()~~>getConnection()~~>query($dql, $id);
$related = $coll[0];

As you can see it accesses the first element by using index "0" in $coll and hence ignores a modified ATTR_COLL_KEY-setting, for instance:

$this->setAttribute(Doctrine_Core::ATTR_COLL_KEY, 'id');

Fortunately I had two models (ForeignA and ForeignB) in my project which both have an one-to-one relation to a third model (Main). That helped me finding this bug which causes the following strange behavior:

// program 1:

$m = new Main();
$m->name = 'M1';
$m->setForeignA(new ForeignA()); // has ATTR_COLL_KEY changed to 'id'
$m->setForeignB(new ForeignB());
$m->save();

// program 2:

$m = Doctrine_Core::getTable('M1')->findOneBy('name', 'M1');
$m->getForeignA()->exists(); // false
$m->getForeignB()->exists(); // true

-------------------------

The big problem about this issue is that behavior is inconsistent. If you don't split the example above into two separate programs/processes you won't have problems, since Doctrine accesses the reference which was stored when calling save().

You will get into trouble using functional tests in Symfony. Since there is only a single process for all requests I wasn't able to reproduce a problem caused by this bug which appeared in the production environment.

-------------------------

Edit:

Doctrine_Connection::queryOne() is affected as well!

A solution is to replace

$coll = $this->getTable()~~>getConnection()~~>query($dql, $id);
$related = $coll[0];

$related = $this->getTable()~~>getConnection()~~>query($dql, $id)->getFirst();

[DC-1052] limit() get lost on multiple joins

Tue, 20 Mar 2012 13:37:12 +0000

$strSql = UserFeedTable::getInstance()~~>createQuery('q')~~>
select('q., f., fi., fav.')->
leftJoin('q.Feed f')->
leftJoin('f.FeedItem fi')->
leftJoin('fi.Favorite fav')->
andWhere('q.profile_id = ?', $intUserId)->
andWhere('q.is_active = ?', true)->
limit(10)->getSqlQuery();
var_dump($strSql);

string(1075) "SELECT u.id AS u_id, u.name AS uname, u.image AS uimage, u.lead AS ulead, u.headline AS uheadline, u.sort AS usort, u.is_active AS uis_active, u.is_favorite AS uis_favorite, u.feed_id AS ufeed_id, u.profile_id AS uprofile_id, u.category_id AS ucategory_id, u.created_at AS ucreated_at, u.updated_at AS uupdated_at, f.id AS fid, f.url AS furl, f.name AS fname, f.created_at AS fcreated_at, f.updated_at AS fupdated_at, f2.id AS f2id, f2.lead AS f2lead, f2.description AS f2description, f2.image AS f2image, f2.pub_date AS f2pub_date, f2.link AS f2link, f2.feed_id AS f2feed_id, f2.created_at AS f2created_at, f2.updated_at AS f2updated_at, f3.id AS f3id, f3.profile_id AS f3profile_id, f3.feed_item_id AS f3feed_item_id, f3.created_at AS f3created_at, f3.updated_at AS f3_updated_at FROM user_feed u LEFT JOIN feed f ON u.feed_id = f.id LEFT JOIN feed_item f2 ON f.id = f2.feed_id LEFT JOIN favorite f3 ON f2.id = f3.feed_item_id WHERE u.id IN ('7', '8', '9', '10', '11') AND (u.profile_id = ? AND u.is_active = ?)"

As you can see, the limit is missing.

[DC-1053] Renaming a doctrine 'string' field may result in loss of data as the field's type changes. (MySQL)

Mon, 26 Mar 2012 20:52:02 +0000

Consider the following schema:

schema.yml

MyTable:
  columns:
    some_text:        string

Doctrine creates the table with:

CREATE TABLE `my_table` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `some_text` text,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Now, the following migration should rename the field from some_text to just_text:

<?php
class Version1 extends Doctrine_Migration_Base
{
    public function up()
    {
        $this->renameColumn('my_table', 'some_text', 'just_text');
    }

    public function down()
    {
      $this->renameColumn('my_table', 'just_text', 'some_text');
    }
}

...however the field gets renamed and the type becomes VARCHAR(255), as the resulting SHOW CREATE TABLE my_table shows:

CREATE TABLE `my_table` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `a_varchar` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Causes data in the column greater than 255 bytes to get truncated

[DC-1058] Warning: Invalid argument supplied for foreach() in SqlWalker.php line 899

Sun, 29 Jul 2012 09:44:56 +0000

Hallo, i get the error
Warning: Invalid argument supplied for foreach() in /var/www/phverbose/vendor/doctrine/Doctrine/ORM/Query/SqlWalker.php line 899

Here is the line
foreach ($assoc['relationToTargetKeyColumns'] as $relationColumn => $targetColumn) {

Here are the relations and the query
http://pastie.org/4352511
http://pastie.org/4352498

Here is the dump of $assoc before warning

array(16) {
["fieldName"]=>
string(5) "sites"
["joinTable"]=>
array(0) {
}
["targetEntity"]=>
string(13) "Entities\Site"
["mappedBy"]=>
string(6) "emails"
["inversedBy"]=>
NULL
["cascade"]=>
array(1)

{ [0]=> string(7) "persist" }

["orphanRemoval"]=>
bool(false)
["fetch"]=>
int(2)
["type"]=>
int(8)
["isOwningSide"]=>
bool(false)
["sourceEntity"]=>
string(14) "Entities\Email"
["isCascadeRemove"]=>
bool(false)
["isCascadePersist"]=>
bool(true)
["isCascadeRefresh"]=>
bool(false)
["isCascadeMerge"]=>
bool(false)
["isCascadeDetach"]=>
bool(false)
}

[DC-49] Wrong query parameter order when using limit() on PostgreSQL

Mon, 26 Jul 2010 10:01:23 +0000

Trying to add limit() to complex query with many where's and some joins. In pgsql it causes nested limit subquery and in some cases parameter order (when limit subquery exists params array just merges with itself, i. e. (1,2) becomes (1,2,1,2)) makes result query wrong, i. e. params array order doesn't correspond placeholders order in query.

With named query parameters all ok.

Testcase attached.

[DC-67] Taggable not working

Thu, 15 Apr 2010 14:50:14 +0000

After enabling Taggable extension, magic methods on the tables (e.g. getPopularTags)
cannot be reached:

Doctrine::getTable('Upload')->getPopularTags();

Fatal error: Uncaught exception 'Doctrine_Table_Exception' with message 'Unknown method Doctrine_Table::getPopularTags' in C:\Users\user\www\extens.dev\lib\Doctrine\Table.php:2608 Stack trace: #0 [internal function]: Doctrine_Table->__call('getPopularTags', Array) #1 C:\Users\user\www\extens.dev\index.php(7): Doctrine_Table->getPopularTags() #2

{main}

thrown in C:\Users\user\www\extens.dev\lib\Doctrine\Table.php on line 2608

[DC-81] Using WITH in combinations with LIMIT returns unexpected results

Tue, 15 Jun 2010 10:15:33 +0000

When I try to limit left joined records with an additional WITH clause, it seems to be bugged when also specifying a LIMIT.

My DQL:

FROM Transporter t LEFT JOIN t.Profile p LEFT JOIN t.Requests r WITH (r.distributor_id = ?) WHERE t.is_active = ? ORDER BY p.company_country, p.company_name LIMIT 20

This returns me 0 results, while removing the LIMIT (or the WITH) will return me 2 results.

[DC-185] The pessimistic offline locking manager locks the entire table

Thu, 13 Dec 2012 13:12:52 +0000

Scenario:
$entity = Doctrine::getTable('Steps')->find($pID);
$lockingManager = new Doctrine_Locking_Manager_Pessimistic( Doctrine_Manager::connection() );
$lockingManager->releaseAgedLocks(300);
$gotLock = $lockingManager->getLock($entity, 'user1' );

Running this code locks the entire table "Steps", and not just the record.

in the table "doctrine_lock_tracking", in the fields: "object_type" and "object_key" are saved in this case: "Steps" and "IDStep".
I think that here must be saved "Steps" and "120" (the value of IDStep).

[DC-188] Pager breaks when HAVING clause references existing table column

Tue, 20 Jul 2010 01:14:31 +0000

Pager breaks when HAVING clause references any existing table column.

Query used:

$q = Doctrine_Query::create()
->select("u.id, u.first_name, u.last_name, u.is_active")
->addSelect('COUNT(u.id) as rolecount')
->from('User u')
->leftJoin('u.Roles r')
->groupBy('u.id')
->having("rolecount > 2 and u.is_active = 1");

Execution of query by itself works fine (eg via execute(), fetch...)

When putting this query in a Doctrine_Pager, error outputs:

$pager = new Doctrine_Pager(
$q,
$currentPage,
$resultsPerPage
);

$pager->execute();

Error Received:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'u.is_active' in 'having clause'

[DC-254] getLimitSubquery Not Including All Order By Parts

Sun, 27 Feb 2011 18:39:08 +0000

The getLimitSubquery function is only including the first orderby field and ignoring all remaining parts. The function also needs to be changed to include mssql and odbc.

The diff's below provide corrections.

Thanks,

Mike

diff -r Doctrine-1.1.2\lib\Doctrine\Query.php Doctrine-1.1.2-Fixes\lib\Doctrine\Query.php
1367c1367
<         if ($driverName == 'pgsql' || $driverName == 'oracle' || $driverName == 'oci') {
---
>         if ($driverName == 'pgsql' || $driverName == 'oracle' || $driverName == 'oci' || $driverName == 'mssql' || $driverName == 'odbc') {
1371,1387c1371,1392
<                 $part_original = trim($e[0]);
<                 $callback = create_function('$e', 'return trim($e, \'[]`"\');');
<                 $part = trim(implode('.', array_map($callback, explode('.', $part_original))));
< 
<                 if (strpos($part, '.') === false) {
<                     continue;
<                 }
< 
<                 // don't add functions
<                 if (strpos($part, '(') !== false) {
<                     continue;
<                 }
< 
<                 // don't add primarykey column (its already in the select clause)
<                 if ($part !== $primaryKey) {
<                     $subquery .= ', ' . $part_original;
<                 }
---
> 
>                 foreach ($e as $f) {
>                     if ($f == 0 || $f % 2 == 0) {
>                         $part_original = trim($f);
>                         $callback = create_function('$e', 'return trim($e, \'[]`"\');');
>                         $part = trim(implode('.', array_map($callback, explode('.', $part_original))));
> 
>                         if (strpos($part, '.') === false) {
>                             continue;
>                         }
> 
>                         // don't add functions
>                         if (strpos($part, '(') !== false) {
>                             continue;
>                         }
> 
>                         // don't add primarykey column (its already in the select clause)
>                         if ($part !== $primaryKey) {
>                             $subquery .= ', ' . $part_original;
>                         }
>                     }
>                 }

[DC-278] Invalid qubquery generated if using oracle adapter instead of pdo_oci

Wed, 9 Jun 2010 13:02:31 +0000

Doctrine generates the following invalid subquery if oracle adapter is used (same query is generated corret if pdo_oci is used):

SELECT DISTINCT "s2"."code"
FROM "spend_category" "s2"
INNER JOIN "company_spend_category" "c4" ON ("s2"."code" = "c4"."spendcategory_code")
INNER JOIN "company" "c3" ON "c3"."code" = "c4"."company_code"
WHERE "s2"."code" = '19000000'
AND "c3"."is_deleted" IS NOT NULL
AND "s2"."is_deleted" IS NOT NULL
ORDER BY "c3"."name" desc

The problem is that the order by column is not part of the selected columns.

Sample dql statement to reproduce this error:

$this->pageAllPager = new Doctrine_Pager(
$q = Doctrine_Query::create()
->select('c.code, c.name, c.is_activated, c.is_deleted, sc.code')
->from('SpendCategory sc')
->innerJoin('sc.Companies c')
->where("sc.code = '$spendcategory'")
->addWhere('c.is_deleted IS NOT NULL')
->addWhere('sc.is_deleted IS NOT NULL')
->orderBy($orderBy)
->setHydrationMode(Doctrine::HYDRATE_ARRAY),
$page,
$resultsPerPage);
}

[DC-280] Add pre/postHydrateResultSet() events

Tue, 8 Jun 2010 16:09:38 +0000

Over the last several weeks I've been working on streamlining the access control logic in the application I'm working on, and I realized that Doctrine's event listeners might be able to help. For more detailed background information take a look at http://groups.google.com:80/group/dallasphp/browse_thread/thread/91e3f107cd611adf ...but here's the problem in a nutshell:

Since my application's access control logic is all implemented in PHP rather than in the database (i.e., I can't add access control to my queries as a simple WHERE clause), I'm looking for a way to hook into the query process just after the records have been hydrated and actually modify the result set that gets returned, such that only permissible records show up in the final result set.

Unfortunately, although there are several listener methods that look promising for this, none of them seem to have access to the data being returned. For instance, if I run a custom query via Doctrine_Query::execute(), the postQuery() hook definitely runs ...but it doesn't give me access to anything but the query string itself.

Since, in some instances (e.g., hydration listeners), the Doctrine_Event object is assigned arbitrary data that the listener can modify, I'm wondering if the same thing couldn't be done more universally?

[DC-287] Schema: package property for model

Tue, 8 Jun 2010 16:19:51 +0000

There is a property "package" for the schema.yml file.
http://www.doctrine-project.org/documentation/manual/1_0/en/yaml-schema-files#features-examples:packages

But this should be used only for plugin symfony.

It will be good to have the same feature for classic model (not plugin), to be available to organize the model inside of the model folder.

This feature is critical for huge project. Indeed having 200 files at the root of the folder model/doctrine is very difficult to maintain.

[DC-290] Relations need alias

Wed, 9 Jun 2010 16:08:24 +0000

While implementing a Record_Template and manipulating a query by using the preDqlSelect Event, i got massive problems if the query was generated by a refresh() or refreshRelated() call. I found out that the issue appears because the query has no alias for the table then. This makes it hard to add forther (sub-)selects to the query via preDqlSelect, e.g.

$params = $event->getParams();
		$alias = $params['alias'];

                if(!$query->isSubquery() && $alias == $queryClone->getRootAlias()) {	
				
				
				$countQuery = '(SELECT COUNT('.$alias.'_tcount.uid) FROM '.$modelName.' '.$alias.'_tcount WHERE '.$alias.'.'.$groupId.'='.$alias.'_tcount.'.$groupId.') AS '.$this->_options['terminationCount'];
				
				$query->addSelect($countQuery);
			}

The issue is solved by adding an alias in the foreignKey and localKey relation types' fetchRelatedFor methods (at least that's sufficient for my issue, maybe there is a need to add similar lines to the other relation types).

Doctrine_Relation_ForeignKey (from line 60):

$alias = $this->getTable()->getComponentName().'_rel';
            	
                $dql  = 'FROM ' . $this->getTable()->getComponentName()
                      .' '.$alias. ' WHERE ' . $this->getCondition($alias) . $this->getOrderBy(null, false);

Doctrine_Relation_LocalKey (from line 58):

$alias = $this->getTable()->getComponentName().'_rel';
        	
            $dql  = 'FROM ' . $this->getTable()->getComponentName()
                 .' '.$alias. ' WHERE ' . $this->getCondition($alias) . $this->getOrderBy(null, false);

[DC-292] no migrations diff on template change

Mon, 1 Mar 2010 19:44:09 +0000

the generate-migrations-diff does not create migrations if the template changes fields on the model.

For example:

File:
tableName: files
inheritance:
extends: Eeecore_Record_File
actAs:
Fileable:

The Fileable Template does the following... (the "fileFields" option stores a couple of fields to add to the model)

public function setTableDefinition()
{

foreach ($this->_options['fileFields'] as $key => $field)

{ $this->hasColumn($field['name'], $field['type'], $field['length'], $field['options']); }

}

everything works fine on generate-migrations-models (the initial migrations)... but if we change something on the "fileFields" the generate-migrations-diff call doesn't do anything. We have to rebuild all migrations or write a new migration by hand.

[DC-293] Implement a self-reference class mechanism without the usage of associative classes

Wed, 25 Nov 2009 17:59:51 +0000

Implement a self-reference class mechanism without the usage of associative classes

[DC-312] Doctrine_Pager query "influences" Doctrine::getTable() query

Wed, 2 Dec 2009 10:20:19 +0000

When I use the same procedure without Doctrine_Pager everything works fine, with Doctrine_Pager the behavior of later queries is strange. Example:
----------------WORKING:
1. I fetch list
Doctrine_Query::create()~~>select('z.,s.,o.*,u.jmeno as Vložil,k.nazev_cs as Kategorie')~~>from('ShopZbozi z,z.Obrazek o,z.Soubor s,z.Uzivatel u,z.ShopKategorie k')~~>orderby('z.nazev_cs ASC')~~>fetchArray();

2. I fetch a row to edit independently on the list above
$object = Doctrine::getTable('ShopZbozi')->find(123);

3. edit properties of the object...

4. $object->replace();
the object is fetched with no related objects like [Uzivatel] or [Soubor], so when I change for example $object->iduzivatel (related Uzivatel object id) and save it is OK

----------------BROKEN:
1. I fetch list in Pager
new Doctrine_Pager(Doctrine_Query::create()~~>select('z.,s.,o.*,u.jmeno as Vložil,k.nazev_cs as Kategorie')~~>from('ShopZbozi z,z.Obrazek o,z.Soubor s,z.Uzivatel u,z.ShopKategorie k')~~>orderby('z.nazev_cs ASC'),$this~~>page,$this->perpage);

2. I fetch a row to edit independently on the list above (in contrast to the first working example this $object is fetched with EMPTY RELATION OBJECTS, which causes inserting empty new rows when calling ->replace())
$object = Doctrine::getTable('ShopZbozi')->find(123);

3. edit properties of the object...

4. $object->replace();
-> the $object has all the related object fetched as it was defined in the list in Pager - like it was used as a template for getTable and when ->replace() - new empty related objects are inserted in DB.

I've been using Doctrine for I guess 2 years now and I believe this bug/strange behavior has always been there.
Maybe I'm wrong and it is not a bug, but the behavior is strange and it took me really long to find where the problem is and I still don't know how to use pager without influencing the later queries.
Thanx John Mathew

[DC-321] Doctrine/Import/Mssql.php does not handle default values

Thu, 3 Dec 2009 20:16:02 +0000

If I generate models from sql server I notice that the default values are empty although some columns in the database do have default values.

I did 'EXEC sp_columns @table_name = 'page';' in sql server and I could clearly see default values in 'column_def' so somehow the default values get lost.

[DC-322] Data dump fails on tables with quoted identifiers

Fri, 4 Dec 2009 17:03:56 +0000

While dumping a table with a quoted identifier `numeric`, doctrine failed because the constructed query had an invalid alias the field: c__`numeric`.

Output:
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '`numeric`, c.alpha3 AS c_alpha3, c.alpha2 AS calpha2 FROM country_codes c' at line 1. Failing Query: "SELECT c.country AS ccountry, c.`numeric` AS c`numeric`, c.alpha3 AS calpha3, c.alpha2 AS c_alpha2 FROM country_codes c"

I know that using quoted identifiers is discouraged but I think this could be easily solvable.

Thanks.

[DC-325] doctrine pager class with sql server stored procedure

Fri, 4 Dec 2009 04:46:11 +0000

i am using doctrine pager class for pagination in symfony but not able to find any help how i can i use it

i am using sql server stored procedures for fetching databasae .

Thnaks

Khurram

[DC-326] Running out of memory while executing single record lookup.

Mon, 7 Dec 2009 21:06:03 +0000

I have the model class as follows:

schema.yml

options:
  collate: utf8_unicode_ci
  charset: utf8
  type: INNODB
Identity:
  tableName: Identity
  columns:
    id:
      type: integer(4)
      fixed: false
      unsigned: false
      primary: true
      autoincrement: true
    username:
      type: string(50)
      fixed: false
      unsigned: false
      primary: false
      notnull: true
      autoincrement: false
    email:
      type: string(50)
      fixed: false
      unsigned: false
      primary: false
      notnull: true
      autoincrement: false
    password:
      type: string(100)
      fixed: false
      unsigned: false
      primary: false
      notnull: true
      autoincrement: false
    created_at:
      name: created_at
      type: timestamp
      # default: CURRENT_TIMESTAMP
      fixed: false
      unsigned: false
      primary: false
      notnull: true
      autoincrement: false
    updated_at:
      name: updated_at
      type: timestamp
      fixed: false
      unsigned: false
      primary: false
      default: null
      notnull: false
      autoincrement: false
  relations:
    Roles:
      class: Role
      local: id
      foreign: ident_id
      type: many
    Token:
      local: id
      foreign: entity_id
      type: many
    Devices:
      class: Device
      local: id
      foreign: account_id
      type: many
    Rides:
      class: Ride
      local: id
      foreign: account_id
      type: many
    OwnGroups:
      class: CoachGroup
      local: id
      foreign: owner_id
      type: many
    GroupMemberships:
      class: GroupMembership
      local: id
      foreign: ident_id
      type: many
  actAs:
    Timestampable:
      created:
        name: created_at
        type: timestamp
        expression: NOW()
      update:
        onInsert: false
Role:
  tableName: Role
  columns:
    identId:
      name: ident_id
      type: integer(4)
      fixed: false
      unsigned: false
      primary: true
      autoincrement: false
    role:
      type: string(50)
      fixed: false
      unsigned: false
      primary: true
      autoincrement: false
  relations:
    Identity:
      onDelete: CASCADE
      onUpdate: CASCADE
      local: ident_id
      foreign: id
      foreignAlias: Roles
Token:
  tableName: Token
  columns:
    entity_id:
      name: entity_id
      type: integer(4)
      fixed: false
      unsigned: false
      notnull: true
      primary: false
      autoincrement: false
    token:
      name: token
      type: string(50)
      fixed: true
      unsigned: false
      primary: true
      default: ''
      notnull: true
      autoincrement: false
    type:
      type: enum(50)
      fixed: false
      unsigned: false
      values:
        - EMAIL_VERIFICATION
        - PASS_RESET
      primary: false
      default: EMAIL_VERIFICATION
      notnull: true
      autoincrement: false
    created_at:
      type: timestamp(25)
      fixed: false
      unsigned: false
      primary: false
      notnull: true
      autoincrement: false
    expires_at:
      type: timestamp(25)
      fixed: false
      unsigned: false
      primary: false
      notnull: false
      autoincrement: false
  indexes:
    entity:
      fields: [entity_id]
  relations:
    Identity:
      onDelete: CASCADE
      onUpdate: CASCADE
      local: entity_id
      foreign: id
      type: one
  actAs:
    Timestampable:
      created:
        name: created_at
        type: timestamp
      updated:
        disabled: true

and my unit test for the model:

TokenModelTest.php

$t = new lime_test(3);
$t->diag("=== Token model test ===");

$t->info('Token creation =>');
$token = new Token();
$token->setEntityId(1);
$token->generateUniqueToken();

$t->info('Set valid token type...');
$token->setType(Token::TYPE_EMAIL_VERIFICATION);
try{
  $t->info('Saving the token...');
  $token->save();
  $t->pass('Token was saved successfully...');
}
catch(Exception $e){
  $t->is(($e instanceof Exception), true, $e->getMessage());
}

$t->isnt($token->getCreatedAt(), null, ' Creation datetime is set to '.$token->getCreatedAt().'...');

$t->info('Get this token from DB...');
$tokenFromDb = Doctrine::getTable('Token')->findOneByToken($token->getToken());

$t->info('Compare the two...');
$t->is($tokenFromDb->getEntityId(), $token->getEntityId(), 'Entity ID...');
$t->is($tokenFromDb->getToken(), $token->getToken(), 'Token string...');
$t->is($tokenFromDb->getType(), $token->getType(), 'Token string...');
$t->is($tokenFromDb->getCreatedAt(), $token->getCreatedAt(), 'Token creation date...');
$t->is($tokenFromDb->getExpiresAt(), $token->getExpiresAt(), 'Token expration date...');
$t->is($tokenFromDb->getExpiresAt(), null, 'Token expration date is null...');

$t->info('Delete token...');
$t->is($token->delete(), true, 'Successful deletion...');

On test execution on this line:

$tokenFromDb = Doctrine::getTable('Token')->findOneByToken($token->getToken());

I'm getting a fatal error:

ERROR

# === Token model test ===
> Token creation =>
> Set valid token type...
> Saving the token...
ok 1 - Token was saved successfully...
ok 2 -  Creation datetime is set to 2009-12-04 01:13:31...
> Get this token from DB...
PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 261900 bytes) in /ApacheWebServer/htdocs/Clients/enki/enkiweb/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Core.php on line 550

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 261900 bytes) in /ApacheWebServer/htdocs/Clients/enki/enkiweb/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Core.php on line 550

[DC-328] Multi-table query (left-join) problem in the Doctrine_Hydrator_Graph class

Fri, 4 Dec 2009 18:13:37 +0000

I tried below code. It must be return 2 records, but It returned 1 record. I traced Doctrine and found to reason in
Doctrine_Hydrator_Graph class line 165 ( $identifierMap[$rootAlias][$id[$rootAlias]] = $this->getLastKey($result); ) When couple $rootAlias not get record.

I attached my data and code. Is it problem?!

77 $q = Doctrine_Query::create();
78 $q->select("r.post_id as id, p.title as title, p.slug as slug, p.created_on as created_on")->
79 from("Relations r")->
80 leftJoin("r.Taxonomies t")->
81 leftJoin("t.Marks m")->
82 leftJoin("r.Posts p")->
83 where("m.slug = ?", $slug)->
84 andWhere("m.status = ?", self::PUBLISH)->
85 andWhere("p.status = ?", self::PUBLISH)->
86 andWhere("t.status = ?", self::PUBLISH)->
87 andWhere("t.type = ?", self::CATEGORY)->
88 orderBy("p.created_on desc");

[DC-329] Problem saving Self Referencing (Nest Relations)

Fri, 3 Jun 2011 13:14:55 +0000

There is a problem when you save Many to Many Self Referencing (Nest Relations).

I used the same example that it's used on Doctrine 1.2 Self Referencing (Nest Relations) Documentation:

My Schema:

User:
columns:
name:

Unknown macro: { type}

relations:
Parents:
class: User
local: child_id
foreign: parent_id
refClass: UserReference
foreignAlias: Children

UserReference:
columns:
parent_id:
type: integer
primary: true
child_id:
type: integer
primary: true

Fixtures:

User:
james:
name: James
alexander:
name: Alexander
david:
name: David

The problem happens with the Children. The first time I assigned children and saved the User, there is no problem; but when I saved the User again (without any change on him) the values in the UserReference? table changes: the "parent_id" takes the value of the "child_id".

I test it with Sf 1.4 and with Sf 1.3 stable versions, and I've got the same error.

If it not clear to understand what I'm saying, I put a "very ilustrative" image about the form and how change the values of the UserReference? table. Please see it, because it would be very usefull for understanding (explains better than my terrible English)

Thanks for all your work!

P. D.

I forgot to to say that watching the stack trace I think that the problem is in:

symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Connection/UnitOfWork.php

In the line 429:

public function saveAssociations(Doctrine_Record $record)

I would like to help more, but I couldn't figure out how this function works.

[DC-331] Wrong SQL output from Doctrine_Expression for pgsql with timestamp with time zone field

Tue, 5 Jan 2010 00:26:29 +0000

(1) pgsql connection
(2) timestamp with time zone column
(3) $doctrine_expression = new Doctrine_Expression('NOW()');
echo $doctrine_expression->getSQL();
gives:
LOCALTIMESTAMP(0)

What I'd like to get access to using that Doctrine construct is the
functionality of 'CURRENT_TIMESTAMP', (has time zone,
stores time in TIMESTAMP WITH TIME ZONE columns in UTC time)

Fortunately, all the databases that I want to use implement
'CURRENT_TIMESTAMP', but not all PDO/Doctrine databases
support that construct, even though it's ANSI SQL standard,
(which ANSI I don't know.)

[DC-335] Oracle identifier too long in normal SELECT when using longer table name or column

Wed, 13 Oct 2010 18:28:25 +0000

Unfortunatelly oracle has max identifier length for 30 characters. When using longer model names eg. misCompanyContributor with column names the generated aliases for selected columns mix tableized modelname with colum name joined by two __, and sometimes the generated alias should exceed the allowed 30 characters long identifiers, and oracle complains with:

An example of large select with alias:
{{
SELECT
...
mis_contributor.contributor_id AS mis_contributor__contributor_id
..
FROM mis_contributor ...
}}

[DC-338] Add setting charset to sandbox

Thu, 10 Dec 2009 19:23:51 +0000

I try set charset adding to config.php in sandbox:
$manager = Doctrine_Manager::getInstance();
$manager->openConnection(DSN, 'doctrine');
$manager->setAttribute(Doctrine_Core::ATTR_MODEL_LOADING, Doctrine_Core::MODEL_LOADING_PEAR);
$manager->setCharset('utf8');

and this doesn't work.

Please update sandbox and give the how to right setCharset in this example. Almost used utf8.

[DC-339] Documentation unclear about linking inherited objects

Tue, 8 Dec 2009 08:57:45 +0000

The (very nice) doctrine documentation fails to mention anything about how inherited objects handle relations.

I.e. if I got the model:
Entity:
columns:
username: string(20)
password: string(16)
created_at: timestamp
updated_at: timestamp

User:
inheritance:
extends: Entity
type: column_aggregation
keyField: type
keyValue: 1

Group:
inheritance:
extends: Entity
type: column_aggregation
keyField: type
keyValue: 2

Topic:
content: string
entity_id: integer
relations:
User:
class: Entity
local: entity_id
foreign: id

Can I then define both users and groups to link to Topic?

[DC-344] Trouble with auto including generate Base class with specifik name

Sun, 21 Mar 2010 00:34:59 +0000

I have found a problem during testing example model on page http://www.doctrine-project.org/documentation/cookbook/1_1/en/code-igniter-and-doctrine . A use YAML model with object name UserGroup and call method Doctrine_Core::createTablesFromModels('models'); process faling with error:

Fatal error: Class 'BaseUserGroup' not found in /sourcepath/models/UserGroup.php on line 13

Generate model file included abstract class BaseUserGroup exist and is OK. If I include BaseUserGroup manuly or rename object "UserGroup" on "UserGroups" everithing work fine. I thing here is a problem with autoloding base class with specifik name.

Here is my code example:

Doctrine_Core::dropDatabases();
Doctrine_Core::createDatabases();
Doctrine_Core::generateModelsFromYaml('sourcepath/yaml/model.yml', 'models');
Doctrine_Core::createTablesFromModels('models');

Trouble shotting YAML model is:
—
UserGroup:
columns:
user_id:
type: integer(4)
primary: true
group_id:
type: integer(4)
primary: true

[DC-348] Doctrine manual does not document that columns can be added with simple inheritance, or the semantics of accessing those columns in the parent

Thu, 10 Dec 2009 00:23:00 +0000

The Doctrine manual's section on inheritance mentions simple inheritance only briefly. The examples do not show that columns can be added, nor do they explain that the parent model class can also access those columns (very useful when you override its methods at the application level in Symfony).

Both behaviors are supported (Jon suggested I take advantage of them at one point) but it's easy to miss the fact that they are available. For a long time I assumed column aggregation inheritance was the only way to add columns.

I'm now exploiting simple inheritance as a way to add columns to sfGuardUser rather than introducing an sfGuardUserProfile class with all of the attendant problems of trying to pretend two tables are actually one table. This is very useful.

(Out of curiosity, is there an alternative way to add columns to plugin schemas at the app level in Symfony 1.3 similar to the way it's now done for Propel?)

[DC-353] Doctrine_Query can't map a main query colum inside a subquery with join

Thu, 10 Dec 2009 23:17:04 +0000

If i have the following schema:

Medidor:
  tableName: TBLMEDIDOR
  columns:
    CODIGO:
      name: NRCODIGO as codigo
      type: integer(10)
      primary: true
      sequence: SEQMEDCODIGO
    DESCRICAO:
      name: TXDESCRICAO as descricao
      type: string(1000)
      notnull: true

AnaliseMedidor:
  tableName: TBLANALISE_MEDIDOR
  columns:
    CODIGO:
      name: NRCODIGO as codigo
      type: integer(10)
      primary: true
      sequence: SEQANMCODIGO
    DATA:
      name: DTDATA as dataAnalise
      type: date
      notnull: true
    MEDIDOR:
      name: FKMEDCODIGO as medidor_codigo
      type: integer(10)
      notnull: true
    OBSERVACAO:
      name: TXOBSERVACAO as observacao
      type: string(1000)
  relations:
    Medidor: { local: medidor_codigo, foreign: codigo, foreignAlias: Analises }

and execute the following query:

$query = Doctrine::getTable('Medidor')->createQuery()
    ->innerJoin('m.Analises a')
    ->where('a.dataAnalise = (SELECT MAX(a2.dataAnalise) FROM '
        . 'AnaliseMedidor a2 WHERE a2.medidor_codigo = a.medidor_codigo)');

the "a.medidor_codigo" in the subquery don't get correctly mapped. So Doctrine tells me:

{sfDoctrineLogger} executeQuery : SELECT t.nr80102codigo AS t__nr80102codigo, t.tx80102descricao AS t__tx80102descricao FROM TBL80102MEDIDOR t INNER JOIN TBL80103ANALISE_MEDIDOR t2 ON t.nr80102codigo = t2.fk80102codigo WHERE t2.dt80103data = (SELECT MAX(t3.dt80103data) AS t3__0 FROM TBL80103ANALISE_MEDIDOR t3 WHERE t3.fk80102codigo = t2.medidor_codigo)
{Doctrine_Connection_Oracle_Exception} SQLSTATE[HY000]: General error: 904 OCIStmtExecute: ORA-00904: "T2"."MEDIDOR_CODIGO": invalid identifier
 (/root/PDO_OCI-1.0/oci_statement.c:142)

If i put the real name column it runs ok:

$query = Doctrine::getTable('Medidor')->createQuery()
    ->innerJoin('m.Analises a')
    ->where('a.dataAnalise = (SELECT MAX(a2.dataAnalise) FROM '
        . 'AnaliseMedidor a2 WHERE a2.medidor_codigo = a.FKMEDCODIGO)');

But, this should not be done, right?

In Doctrine 1.2 it works fine. But in the related versions don't.

[DC-355] Call to a member function evictAll() if a table is retrieved, that is not existent

Sat, 12 Dec 2009 18:27:17 +0000

Hi!

Im not quite sure it this bahaviour is wanted, but i think that this
should be catched:

If i call Doctrine::getTable on a non existing model, the exception is
thrown. After them i want always to clear all Record Repositories, see
code:

try

{ $table = Doctrine::getTable('notexistent'); }

catch(Exception $e)

{ echo 'not existent'.$e->getMessage(); }

Doctrine_Manager::connection()->clear();

Then I get the error message:

Fatal error: Call to a member function evictAll() on a non-object in /
core/lib/Doctrine/Doctrine/Connection.php on line 1239

The problem is that the function clear doesnt check if a repository is
given.

public function clear()
{
foreach ($this->tables as $k => $table)

{ $table->getRepository()->evictAll(); // getRepository delivers FALSE $table->clear(); }

}

Is it normal behaviour? Or should it be checked first:

if ($repository = $table->getRepository())

{ $repository->evisctAll(); }

best regards,
aNj

[DC-356] Error in self referencing (nest relations) and tableName.

Thu, 17 Jan 2013 01:16:07 +0000

I have this schema:

Interface
Interfaz:
tableName: YT_INTERFAZ
columns:
cinterfaz: { type: integer, notnull: true, primary: true, autoincrement: true }
relations:
Conexiones:
class: Interfaz
local: cinterfazsrc
foreign: cinterfazdst
refClass: Conexion
equal: true

#Link
Conexion:
tableName: YT_CONEXION
columns:
cinterfazsrc:

{ type: integer, primary: true }

cinterfazdst:

{ type: integer, primary: true }

When I try to get $interfaz->Conexiones, I get this message:

Notice: Undefined index: yt_interfaz in /home/sergio/Proyectos/syc/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Hydrator/Graph.php on line 288

Notice: Undefined index: in /home/sergio/Proyectos/syc/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Hydrator/Graph.php on line 289

Fatal error: Call to a member function getFieldName() on a non-object in /home/sergio/Proyectos/syc/lib/vendor/symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Hydrator/Graph.php on line 290

But If I remove tableName fields in schema declaration, it works perfectly. The name of tableName don't matters, if you use it, it fails.

[DC-357] setting "Doctrine_Core::ATTR_EXPORT" to "Doctrine_Core::EXPORT_TABLES" prevents i18n table creation

Mon, 14 Dec 2009 16:51:11 +0000

When I try to prevent foreign key creation (because I am using a mix of MyISAM and InnoDB tables) using the given attribute, I notice that all the translation tables are also not getting created.

[DC-359] concrete inheritance doesn't create all relations

Wed, 16 Dec 2009 19:42:00 +0000

This is the YML schema

Entity:
  actAs:
    Timestampable:
  columns:
    id:
      type: integer(11)
      primary: true
      autoincrement: true
    name: string(50)
  relations:
    DynamicFields:
      class: DynamicField
      local: id
      foreign: dynamic_field_id
      refClass: EntityDynamicFields

DynamicField:
  actAs:
    I18n:
      fields: [name_xml]
  columns:
    id:
      type: integer(11)
      primary: true
      autoincrement: true
    name_xml: 
      type: string(50)
      notnull: true
  relations:
    Entities:
      class: Entity
      local: dynamic_field_id
      foreign: id
      refClass: EntityDynamicFields

EntityDynamicFields:
  actAs:
    I18n:
      fields: [value_xml]
  columns:
    id:
      type: integer(11)
      primary: true
    dynamic_field_id:
      type: integer(11)
      primary: true
    value_xml: string(250)

Airline:
  inheritance:
    extends: Entity
    type: concrete

Bank:
  inheritance:
    extends: Entity
    type: concrete

Client:
  inheritance:
    extends: Entity
    type: concrete

Employe:
  inheritance:
    extends: Entity
    type: concrete

Host:
  inheritance:
    extends: Entity
    type: concrete

Partner:
  inheritance:
    extends: Entity
    type: concrete

Person:
  inheritance:
    extends: Entity
    type: concrete

Supplier:
  inheritance:
    extends: Entity
    type: concrete

I run the commands

./doctrine build-all

and

./doctrine rebuild-db

The problem is when I verify if the foreign keys are created, but
these were only created for the "client" and "employee" models, to
"host" does not create the relationship in the MySQL, but if I rename
"host" with a name like "Ent", the relationship is established, or if I rename
the parent model "Entity" to "Zzzzz", all relations are created.

I did several tests, and the only way that the relation is created, is
that the model name, is alphabetically sorted before the parent model name.

This is a part of the dump of MySQL

ALTER TABLE `entity_dynamic_fields`
  ADD CONSTRAINT `entity_dynamic_fields_dynamic_field_id_dynamic_field_id` FOREIGN KEY (`dynamic_field_id`) REFERENCES `dynamic_field` (`id`),
  ADD CONSTRAINT `entity_dynamic_fields_id_airline_id` FOREIGN KEY (`id`) REFERENCES `airline` (`id`),
  ADD CONSTRAINT `entity_dynamic_fields_id_bank_id` FOREIGN KEY (`id`) REFERENCES `bank` (`id`),
  ADD CONSTRAINT `entity_dynamic_fields_id_client_id` FOREIGN KEY (`id`) REFERENCES `client` (`id`),
  ADD CONSTRAINT `entity_dynamic_fields_id_employe_id` FOREIGN KEY (`id`) REFERENCES `employe` (`id`),
  ADD CONSTRAINT `entity_dynamic_fields_id_entity_id` FOREIGN KEY (`id`) REFERENCES `entity` (`id`);

The other foreign keys are missed

you can view the diagram EER created with reverse engineering of MySQL Workbench

[DC-362] Doctrine fails to create correct table structure if model is named "User"

Fri, 8 Jan 2010 20:31:09 +0000

When building models and database structure from YAML schema, Doctrine ignores the behaviors and relations on models if it is named "User":

...

User:  
  actAs:
    Timestampable:
    Sluggable:
      unique: true
      fields: username
      canUpdate: true
  columns:
    id:
      type: integer(4)
      primary: true
      autoincrement: true
    company_id
      type: integer(4)
    timezone_id:
      type: integer(1)
    role_id:
      type: integer(1)
    email:
      type: string(255)
    username:
      type: string(255)
      unique: true
    password:
      type: string(40)
    firstname:
      type: string(255)
    lastname:
      type: string(255)
    last_login:
      type: datetime
  relations:
    Company:
      local: company_id
      foreign: id
    Timezone:
      local: timezone_id
      foreign: id
    Role:
      local: role_id
      foreign: id

...

This creates the following table structure:

CREATE TABLE `user` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `company_id` int(11) DEFAULT NULL,
  `timezone_id` tinyint(4) DEFAULT NULL,
  `role_id` tinyint(4) DEFAULT NULL,
  `email` varchar(255) DEFAULT NULL,
  `username` varchar(255) DEFAULT NULL,
  `password` varchar(40) DEFAULT NULL,
  `firstname` varchar(255) DEFAULT NULL,
  `lastname` varchar(255) DEFAULT NULL,
  `last_login` datetime DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `username` (`username`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

The table structure is both missing foreign key constraints to Company, Timezone and Role. It is also missing columns updated_at and created_at for Timestampable behavior. The slug column for Sluggable behavior is missing, as well.

When looking at the BaseUser::setUp() method it looks as it is supposed to:

class BaseUser extends Doctrine_Record
{

    ....

    public function setUp()
    {
        parent::setUp();
        $this->hasOne('Company', array(
             'local' => 'company_id',
             'foreign' => 'id'));

        $this->hasOne('Timezone', array(
             'local' => 'timezone_id',
             'foreign' => 'id'));

        $this->hasOne('Role', array(
             'local' => 'role_id',
             'foreign' => 'id'));

        $timestampable0 = new Doctrine_Template_Timestampable();
        $sluggable0 = new Doctrine_Template_Sluggable(array(
             'unique' => true,
             'fields' => 'username',
             'canUpdate' => true,
        ));
        $this->actAs($timestampable0);
        $this->actAs($sluggable0);
    }

    ....

}

So the only area where it goes wrong, is when generating the queries for creating the model tables. I don't know if the same problem appears with other model names, but it doesn't like models named "User".

If I rename the model to "Person" and rebuild, it all works perfectly as it should.

[DC-368] createTablesFromModels() wants to create already existing FOREIGN KEY constraints

Tue, 24 Aug 2010 04:32:21 +0000

If you create InnoDB tables from a given model directory, the table generator wants to create a foreign key constraint that already exists.

1. Doctrine_Core::generateModelsFromYaml('yaml', 'models');
2. Doctrine_Core::createTablesFromModels('models');
3. Running this setup twice, will print out the following error:

SQLSTATE[HY000]: General error: 1005 Can't create table './dev_mreiche/#sql-930_2cb7.frm' (errno: 121). Failing Query: "ALTER TABLE group_user ADD CONSTRAINT group_user_user_id_user_id FOREIGN KEY (user_id) REFERENCES user(id)". Failing Query: ALTER TABLE group_user ADD CONSTRAINT group_user_user_id_user_id FOREIGN KEY (user_id) REFERENCES user(id)

[DC-370] Doctrine serializes arrays, objects, etc. like 'string', which is never bigger than a TEXT, limited to 65535 characters (in MySQL)

Fri, 29 Jan 2010 12:57:17 +0000

Doctrine supports storing objects and arrays, and implements this via serialize().

However in DataDict/Mysql they are handled like the 'string' type, which means they are subject to the rules there that ensure nothing bigger than a 'TEXT' is ever used to represent them.

TEXT is not a great choice for objects and arrays because it's difficult to ensure they will not exceed 65,535 bytes in size.

This would be most easily fixed by moving them to the next block of case statements there, used for CLOBs. The logic there already picks suitable large types (MEDIUMTEXT and LONGTEXT) as needed, and defaults to LONGTEXT which is a good choice for objects and arrays.

[DC-372] I18n record generator assumes relation alias is the table name

Sun, 20 Dec 2009 14:03:24 +0000

In Doctrine/I18n.php, method setTableDefinition, line 108:

        foreach($relations as $table => $relation) {

But the $relations array key is not a table name, but a relation alias.

So currently the generator assumes the relation alias IS the table name.
When it's not true, the I18n table definition fails.

[DC-373] Relating to Translation table (generated by Doctrine_I18n) doesn't work correctly after resetting connection

Tue, 11 Sep 2012 13:16:23 +0000

Relating to Translation table (generated by Doctrine_I18n) doesn't work correctly after resetting connection.

First, I defined the following schema.yml::

 
  Example:
    actAs:
      I18n:
        fields: [title]
    columns:
        title: string(128)

Next, I prepared the following fixture file::

 
  Example:
    Example_1:
      Translation:
        en:
          title: "Title"
        ja:
          title: "題名"

Next, I run "build-all-reload" task. The table was created and data was loaded.

And I write the following code::

 
  Doctrine_Core::loadModels('models');
  $example = Doctrine_Core::getTable('Example')->find(1);
  
  var_dump(
    $example->Translation['en']->title,
    $example->Translation['ja']->title
  );
  
  Doctrine_Manager::resetInstance();
  Doctrine_Manager::getInstance()->openConnection(DSN, 'doctrine');
  
  $example2 = Doctrine_Core::getTable('Example')->find(1);
  var_dump(
    $example2->Translation['en']->title,
    $example2->Translation['ja']->title
  );

I try executing my code, but I got the following error::

  string(5) "Title"
  string(6) "題名"
  
  Doctrine_Connection_Mysql_Exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'e.title' in 'field list' in /path/to/doctrine/Doctrine/Connection.php on line 1082
  
  Call Stack:
      0.0055      65352   1. {main}() /path/to/my/code/test.php:0
      0.2776    5873388   2. Doctrine_Table->find() /path/to/my/code/test.php:52
      0.2793    5881152   3. Doctrine_Query->fetchOne() /path/to/doctrine/Doctrine/Table.php:1611
      0.2793    5881296   4. Doctrine_Query_Abstract->execute() /path/to/doctrine/Doctrine/Query.php:281
      0.2793    5881892   5. Doctrine_Query_Abstract->_execute() /path/to/doctrine/Doctrine/Query/Abstract.php:1026
      0.3127    5890712   6. Doctrine_Connection->execute() /path/to/doctrine/Doctrine/Query/Abstract.php:976
      0.3164    5892632   7. Doctrine_Connection_Statement->execute() /path/to/doctrine/Doctrine/Connection.php:1006
      0.3181    5907408   8. Doctrine_Connection->rethrowException() /path/to/doctrine/Doctrine/Connection/Statement.php:269

[DC-375] Doctrine_Table getTable singleton issue

Tue, 22 Dec 2009 06:59:07 +0000

first, i defined a table class :
class CohibaClientTable extends Doctrine_Table
{
public $_pager;

public function getAbstractList($arrParam = array(), $page=1, $maxPerPage=20)
{
$objQuery = $this->createQuery('t1')
->select('t1.*');

if(is_array($arrParam) && count($arrParam)>0)

{ QueryAssistant::processOption($objQuery, $arrParam); // dont set "offset" and "limit" option in it }

$this->_pager = new Doctrine_Pager($objQuery, $page, $maxPerPage);

$items = $this->_pager->execute();

$objQuery->free();
return $items;
}

public function getList($page=1, $maxPerPage=20)

{ $arrParam = array( 'orderBy'=>'t1.cle asc' ); return $this->getAbstractList($arrParam, $page, $maxPerPage); }

public function getPager()

{ return $this->_pager; }

}

and then, in the action, invoke it like this codes:
1>
$items = Doctrine::getTable("CohibaClient")->getList(1, $maxPerPage);
$pager = Doctrine::getTable("CohibaClient")->getPager();

$this->log("total records: ".$pager->getNumResults()." total page: ".$pager->getLastPage()."\n");
$lastPage = $pager->getLastPage();
2>
$table = Doctrine::getTable("CohibaClient");
$items = $table->getList(1, $maxPerPage);
$pager = $table->getPager();

$this->log("total records: ".$pager->getNumResults()." total page: ".$pager->getLastPage()."\n");
$lastPage = $pager->getLastPage();

#2 works, but not #1, error is "Fatal error: Call to a member function getNumResults() on a non-object in.... " is it an issue when singleton generation?

[DC-379] No description of ATTR_DEFAULT_IDENTIFIER_OPTIONS now in "Chapter 4 Configuration"

Wed, 23 Dec 2009 02:55:04 +0000

In the previous (1.1) documentation version there were small but useful description about how to set up primary key (http://www.doctrine-project.org/documentation/manual/1_1/en/configuration#defaults-attributes:default-added-auto-id)
Now there is nothing about ATTR_DEFAULT_IDENTIFIER_OPTIONS and it takes about 20 minutes to debug and find out where did "id" field added

ps: message "If you find a problem with the documentation or have a suggestion, please register and open a ticket. " in the bottom of the docs pages is ambiguous due to it points to trac :-$

[DC-383] Migrations not respecting ATTR_TBLNAME_FORMAT

Fri, 28 May 2010 06:13:28 +0000

I am using Doctrine 1.2.1 and Migrations don't appear to respect Doctrine::ATTR_TBLNAME_FORMAT when creating or dropping tables. This means while models create/drop tables with prefixes migrations don't. Also the migration_version table is created without the prefix too even though it was apparently fixed in ~~DC-245~~.

I haven't tested but it also probably means other attributes like Doctrine::ATTR_IDXNAME_FORMAT and Doctrine::ATTR_SEQNAME_FORMAT are not obeyed either which makes things a little confusing knowing when to care for prefixes or not.

[DC-386] Doctrine_Hydrator_ArrayDriver may segfault Php when loaded by Zend Framework Autoloader

Thu, 24 Dec 2009 23:46:23 +0000

Apache and Php segfault with no error information in the logs and a white screen of death when I use Doctrine 1.2.1 in a Zend Framework controller.

I've traced the problem to line 126 of Zend/Loader/Autoloader.php which only seemed to occur when it autoloaded Doctrine_Hydrator_ArrayDriver during a call to save() in the controller.

I debugged with xdebug and have attached a simple test controller with no other code. The ZF page works fine when all Doctrine is commented out and a Doctrine test page with the same code but outside of ZF worked fine via Apache as did a CLI script.

Workaround is to not push Doctrine to Zend Loader in the bootstrap.

Here is the debug output just before a segfault, the stack and the variable values:

Remote Launch (stepping)
Library/Zend/Loader/Autoloader.php.Zend_Loader_Autoloader::autoload : lineno 126
Library/Zend/Loader/Autoloader.php.is_subclass_of : lineno 0
Library/Doctrine/Query.php.Doctrine_Query->processPendingFields : lineno 477
Library/Doctrine/Query.php.Doctrine_Query->buildSqlQuery : lineno 1213
Library/Doctrine/Query.php.Doctrine_Query->getSqlQuery : lineno 1122
Library/Doctrine/Query/Abstract.php.Doctrine_Query_Abstract->_getDqlCallbackComponents : lineno 1137
Library/Doctrine/Query/Abstract.php.Doctrine_Query_Abstract->_preQuery : lineno 1106
Library/Doctrine/Query/Abstract.php.Doctrine_Query_Abstract->execute : lineno 1001
Library/Doctrine/Template/Listener/Sluggable.php.Doctrine_Template_Listener_Sluggable->getUniqueSlug : lineno 207
Library/Doctrine/Template/Listener/Sluggable.php.Doctrine_Template_Listener_Sluggable->buildSlugFromFields : lineno 120
Library/Doctrine/Template/Listener/Sluggable.php.Doctrine_Template_Listener_Sluggable->preInsert : lineno 65
Library/Doctrine/Record/Listener/Chain.php.Doctrine_Record_Listener_Chain->preInsert : lineno 342
Library/Doctrine/Record.php.Doctrine_Record->invokeSaveHooks : lineno 355
Library/Doctrine/Connection/UnitOfWork.php.Doctrine_Connection_UnitOfWork->insert : lineno 551
Library/Doctrine/Connection/UnitOfWork.php.Doctrine_Connection_UnitOfWork->saveGraph : lineno 81
Library/Doctrine/Record.php.Doctrine_Record->save : lineno 1691
Application/controllers/TestingController.php.TestingController->indexAction : lineno 20
Library/Zend/Controller/Action.php.Zend_Controller_Action->dispatch : lineno 513
Library/Zend/Controller/Dispatcher/Standard.php.Zend_Controller_Dispatcher_Standard->dispatch : lineno 289
Library/Zend/Controller/Front.php.Zend_Controller_Front->dispatch : lineno 946
Library/Zend/Application/Bootstrap/Bootstrap.php.Zend_Application_Bootstrap_Bootstrap->run : lineno 77
Application/Bootstrap.php.Bootstrap->run : lineno 52
Library/Zend/Application.php.Zend_Application->run : lineno 346
Public/index.php.

{main}

: lineno 26

=====-=

$class Doctrine_Hydrator_ArrayDriver
$object Zend_Loader_Autoloader
_autoloaders Array [1]
0 Array [2]
0 Doctrine
1 autoload
_defaultAutoloader Array [2]
0 Zend_Loader
1 loadClass
_fallbackAutoloader false
_internalAutoloader Array [2]
0 Zend_Loader_Autoloader
1 _autoload
_namespaces Array [5]
Zend_ true
ZendX_ true
Lisantra_ true
Persistence_ true
Doctrine_ true
_namespaceAutoloaders Array [1]
Array [1]
0 Array [2]
0 Doctrine
1 autoload
_suppressNotFoundWarnings false
$self Zend_Loader_Autoloader
_autoloaders Array [1]
0 Array [2]
0 Doctrine
1 autoload
_defaultAutoloader Array [2]
0 Zend_Loader
1 loadClass
_fallbackAutoloader false
_internalAutoloader Array [2]
0 Zend_Loader_Autoloader
1 _autoload
_namespaces Array [5]
Zend_ true
ZendX_ true
Lisantra_ true
Persistence_ true
Doctrine_ true
_namespaceAutoloaders Array [1]
Array [1]
0 Array [2]
0 Doctrine
1 autoload
_suppressNotFoundWarnings false
$method _autoload
$autoloader Array [0]

[DC-387] mssql fails on find($key)

Tue, 5 Jan 2010 21:37:05 +0000

Doctrine_Core::getTable('Project')->find($id)
this kind of expression produces query like "SELECT TOP 1 [inner_tbl].[id] AS [p__id] FROM (SELECT TOP 1 [p].[id] AS [p__id], [p].[name] AS [p__name], [p].[description] AS [p__description] FROM [project] [p] WHERE ([p].[id] = ?)) AS [inner_tbl]"
which fails because there is no [inner_tbl].[id]

[DC-388] Conservative loading not working

Wed, 27 Jan 2010 23:53:07 +0000

Apparently, when setting Doctrine::MODEL_LOADING_CONSERVATIVE things like Doctrine_Core::createTablesFromModels() don't work. Have to enable aggressive model loading. This has been confirmed on the doctrine-user mailing list.

I took a brief look at the code: I may be missing something but it appears there may be a logic difference in the conservative vs. aggressive model loading method. Aggressive loading uses require_once on all files in the model directory and tries to determine the name of the class inside the file (by doing a difference on the loaded classes). This logic makes sense since the class and file name do not have to match.

However, conservative loading just tries to calculate the class name and store it in an array for later loading by the autoloader. This means there is a huge logic difference in behaviour between these two loading methods since the model class files actually must differ depending on case (specifically, the model class file name must follow a specific format to match the actual class name) otherwise the autoload array will never know the correct name of the class.

I would also like to comment that overall, require_once is a poor choice for performance reasons, it's vastly slower than include_once, but overall the logic should better be adjusted to use plain include (if possible), for performance reasons.

[DC-389] query cache doesn't cache _isLimitSubqueryUsed

Mon, 27 Jun 2011 18:06:25 +0000

The problem is that _isLimitSubqueryUsed is not cached with query cache.
It gets calculated when building query, but when the query is coming
from cache it's not.
Because of this, line 1087 of Query/Abstract.php is never executed,
when coming from cache:
if ($this->isLimitSubqueryUsed() &&
$this->_conn->getAttribute(Doctrine::ATTR_DRIVER_NAME) !==
'mysql')

{ $params = array_merge((array) $params, (array) $params); } Maybe it is on purpose, but I didn't get any answer on the google-groups. Here is a diff I use now: Index: trunk/gui/doctrine-library/Doctrine/Query/Abstract.php =================================================================== --- a/trunk/gui/doctrine-library/Doctrine/Query/Abstract.php +++ b/trunk/gui/doctrine-library/Doctrine/Query/Abstract.php @@ -1286,4 +1286,5 @@ $cached = unserialize($cached); $this->_tableAliasMap = $cached[2]; + $this->_isLimitSubqueryUsed = $cached[3]; $customComponent = $cached[0]; @@ -1346,5 +1347,5 @@ }

return serialize(array($customComponent, $componentInfo,
$this->getTableAliasMap()));
+ return serialize(array($customComponent, $componentInfo,
$this->getTableAliasMap(), $this->isLimitSubqueryUsed()));
}

[DC-390] doctrine_cache_keys bigger than 1mb

Reference — Wed, 27 Jan 2010 23:33:01 +0000

When multiple projects using doctrine use the same memcached server the doctrine_cache_keys can get bigger then 1mb and php will be throwing warnings telling that the data is too big to be stored by memcached.

I am currently using a workaround, having 1 doctrine_cache_keys per application, on the file Cache/Driver.php i added the following line to the constructor

$this->_cacheKeyIndexKey = 'doctrine_cache_keys_' . md5(Doctrine_Manager::getInstance()->getCurrentConnection()->getOption('dsn'));

but if an application uses more than 1mb en keys then the notice will rise again.

[DC-392] Let the parser ignore .* (hidden) files

Tue, 8 Jun 2010 15:19:18 +0000

When generating models from yml files starting with a `.' such as temporary files from certain editors and meta files from OS X are also parsed by the importer. I do not see any reasons too include these hidden files in parsing as they are hidden for a purpose. And there would be no point in deliberately using hidden files for your config files.

Also see:
http://blog.rajatpandit.com/2009/08/23/doctrine_parser_exception-fail-some-error-message/
and
http://alessandrovermeulen.me/2010/01/01/doctrine-unable-to-parse-string-unable-to-parse-line-0/

[DC-396] Add timezone support for time and timestamp datatype in PostgreSQL

Sun, 19 Aug 2012 05:29:02 +0000

Please add support for the types of time with timezone and timestamp with timezone in the Doctrine when using PostgreSQL.

[DC-400] bit(1) columns are broken

Mon, 11 Apr 2011 15:38:55 +0000

Ihave the following Doctrine schema:

—
TestTable:
columns:
bitty: bit(1)

I have created the database and table for this. I then have the following PHP code:

$obj1 = new TestTable();
$obj1['bitty'] = b'0';
$obj1->save();

$obj2 = new TestTable();
$obj2['bitty'] = 0;
$obj2->save();

Clearly my attempt is to save the bit value 0 in the bitty column.

However after running this PHP code I get the following odd results:

mysql> select * from test_table;
---------+

bitty

---------+

1
2

---------+
2 rows in set (0.00 sec)

mysql> select * from test_table where bitty = 1;
---------+

bitty

---------+

1
2

--------+
2 rows in set (0.00 sec)

mysql> select * from test_table where bitty = 0;
Empty set (0.00 sec)

Those boxes are the 0x01 character, i.e. Doctrine has set the value to 1, not 0.

However I can insert 0's into that table direct from MySQL:

mysql> insert into test_table values (4, b'0');
Query OK, 1 row affected (0.00 sec)

mysql> select * from test_table where bitty = 0;
---------+

bitty

---------+

---------+
1 row in set (0.00 sec)

[DC-401] Doctrine_Query->load crashes with additional ending whitespace in JOIN

Wed, 6 Jan 2010 12:02:40 +0000

following will lead to an error:

->leftJoin('alias.RelatedTable alias2 WITH .....')

The problem is the additional whitespace behind alias2.
On line 1682 in Doctrine_Query class file:

$tmp = explode(' ', $path);

will create an array of 3 elements where the last one is empty but will be used as empty alias mapping after foreach from line 1698.

[DC-402] aliased fields from root class are not recognized als root class fields, if they're the only one

Wed, 6 Jan 2010 14:06:56 +0000

If all selected fields from the root class are aliased,
Doctrine_Query->processPendingFields() won't recognize them as fields of the table and the following exception will be thrown:
"The root class of the query (alias c) must have at least one field selected."

In my real world example, this could only be fixed, using the primary key of the root class/table in select

[DC-403] Eliminate queries produced by Doctrine_Node_NestedSet::getDescendants() when possible

Fri, 16 Apr 2010 12:18:05 +0000

How to reproduce

fetch a tree with nested set

$root = Doctrine::getTable($model)->getTree()->findRoot($rootId);
$treeObject= Doctrine::getTable($model)->getTree()->fetchTree($root->getId());

issue

$root->getNode()->getChildren();

or there will be a total query mess in a lambda function with a loop getChildren().
...
<?php foreach($root->getChildren() as $child): ?>
   ....
<?php endforeach; ?>
...

Problem is described more verbosely here – http://codeutopia.net/blog/2008/08/30/understanding-doctrines-nestedset-feature/

What behavior is expected

An already fetched record instance is returned, without calling database and without causing query flooding.

Like in propel.

In propel if you are calling ....::retrieveTree($id) it returns the root
with completed, pooled (cached) and linked tree.

What happens

An additional query is issued

This is a big slip in architecture of Doctrine`s nested set implementation.

[DC-412] Error defining "unique" constraint in a translated (i18n) column

Sun, 10 Jan 2010 21:18:56 +0000

Let's suppose we have a class "Element" with columns "name" and "description".

We want to set an "unique" constraint in column "name", and set the I18n behavior to columns name and description.

In the generated translation table "element_translation", doctrine sets an unique constraint in the column "name". This is an error, as various languages could translate that string in the same way. I think that the "unique" constraint should be set to the combination of columns "name" and "lang", so the restriction applies for a given language.

[DC-417] Unexpected results with equal many-to-many relations

Thu, 14 Jan 2010 13:05:39 +0000

print_r's before refresh represent what i hoped to get and after that what was inserted into db.

INSERT INTO match_reference (match_id, user_id) VALUES (?, ?)
Array
(
    [0] => 2
    [1] => 1
)


UPDATE match_reference SET match_id = ? WHERE user_id = ? AND match_id = ?
Array
(
    [0] => 1
    [1] => 1
    [2] => 2
)


INSERT INTO match_reference (match_id, user_id) VALUES (?, ?)
Array
(
    [0] => 3
    [1] => 2
)


INSERT INTO match_reference (match_id, user_id) VALUES (?, ?)
Array
(
    [0] => 4
    [1] => 2
)
Array
(
    [0] => Array
        (
            [id] => 2
            [username] => 2
        )

)
Array
(
    [0] => Array
        (
            [id] => 1
            [username] => 1
        )

    [1] => Array
        (
            [id] => 3
            [username] => 3
        )

    [2] => Array
        (
            [id] => 4
            [username] => 4
        )

)
Array
(
)
Array
(
    [0] => Array
        (
            [id] => 3
            [username] => 3
        )

    [1] => Array
        (
            [id] => 4
            [username] => 4
        )

)

schema/schema.yml

---
User:
  columns:
    username: string(255)
  relations:
    Matches:
      class: User
      local: user_id
      foreign: match_id
      refClass: MatchReference
      equal: true
      cascade: [delete]

MatchReference:
  columns:
    user_id:
      type: integer
      primary: true
    match_id:
      type: integer
      primary: true

index.php

require_once('config.php');

Doctrine::loadModels('models');

Doctrine_Query::create()
    ->delete('User')
    ->execute();

Doctrine_Query::create()
    ->delete('MatchReference')
    ->execute();

$u1 = new User();
$u1->id = $u1->username = 1;
$u1->save();

$u2 = new User();
$u2->id = $u2->username = 2;
$u2->save();

$u3 = new User();
$u3->id = $u3->username = 3;
$u3->save();

$u4 = new User();
$u4->id = $u4->username = 4;
$u4->save();

$profiler = new Doctrine_Connection_Profiler();
Doctrine_Manager::getInstance()->getCurrentConnection()->addListener($profiler);

$user_1 = Doctrine::getTable('User')->find(1);

$matches = Doctrine_Query::create()
    ->from('User')
    ->whereIn('id', array(2))
    ->execute(array(), Doctrine::HYDRATE_ARRAY);

$match = $matches[0];

$user_1->link('Matches', array($match['id']));
$user_1->save();

$user_2 = Doctrine::getTable('User')->find(2);

$matches = Doctrine_Query::create()
->from('User')
->whereIn('id', array(3, 4))
->execute(array(), Doctrine::HYDRATE_ARRAY);

foreach ($matches as $match) {
    $user_2->link('Matches', array($match['id']));
}

$user_2->save();

foreach ($profiler as $event) {
    if (in_array($event->getName(), array('execute')) && preg_match('/^(INSERT|UPDATE)/', $event->getQuery())) {
        echo print_r($event->getQuery(), true) . "\n";
        echo print_r($event->getParams(), true) . "\n\n";
    }
}

print_r($user_1->Matches->toArray());
print_r($user_2->Matches->toArray());

$user_1->refresh(true);
$user_2->refresh(true);

print_r($user_1->Matches->toArray());
print_r($user_2->Matches->toArray());

[DC-424] using boolean logic in select don't work

Wed, 27 Jan 2010 21:14:32 +0000

Continuing with same setup as in http://www.doctrine-project.org/jira/browse/DC-417
I discovered another issue

$result = Doctrine_Query::create()
    ->select('u.*, m.*, COUNT(m.id) > 0 AS match_check')
    ->from('User u')
    ->leftJoin('u.Matches m')
    ->groupBy('u.id')
    ->orderBy('match_check DESC, RAND()')
    ->execute(array(), Doctrine::HYDRATE_ARRAY);

match_check will actually be count of matches not 0 or 1 as i expected.
is it bug or feature?

[DC-426] Doctrine incorrectly assigns a NULL value to primary key fields

Thu, 14 Jan 2010 17:25:56 +0000

Hi,

in my project (MySQL 5.x, PHP 5.2.x), I use a combined primary key which looks as follows:

$this->hasColumn("guid", "string", 32, array('primary' => true));
$this->hasColumn("revision", "integer", 4, array('primary' => true));
$this->hasColumn("language", "string", 32, array('primary' => true));

My project automatically initializes the GUID and revision fields, but language is left empty. Doctrine assumes that NULL is a good value, and uses the NULL value after saving an object to reload it. This results in the following statement, generated by the find()-Method within Table.php:

SELECT b.guid AS b_guid, b.revision AS brevision, b.language AS blanguage, b.active AS bactive, b.title AS btitle, b.content AS bcontent, b.category AS b_category FROM blog_entry b WHERE (b.guid = '505f1a2d13864fa4aef461aa1b5b37a3' AND b.revision = '1' AND b.language = NULL)

Since MySQL does not allow NULL values in primary keys, MySQL uses an empty string (''). Doctrine should also use an empty string as default value if the primary key consists of a string, OR issue a warning that MySQL does not allow NULL values in primary keys. The problem with this "bug" is that problems occur in situations where you do not expect them, for example, when storing objects.

If a test case is required, just tell me and I'll prepare one.

Thanks and best regards,
Timo

[DC-427] Record Hydration error

Thu, 14 Jan 2010 19:50:59 +0000

schema.yml

CheCategory:
options:
collate: utf8_unicode_ci
charset: utf8
actAs:
Timestampable: ~
NestedSet: ~
columns:
name:
type: string(255)
CheItem:
options:
collate: utf8_unicode_ci
charset: utf8
actAs:
Timestampable: ~
columns:
name:
type: string(255)
category_id:
type: integer(12)
relations:
CheItemPhoto:
type: many
local: id
foreign: item_id
CheItemAttribute:
type: many
local: id
foreign: item_id
CheCategory:
local: category_id
foreign: id

CheAttribute:
options:
collate: utf8_unicode_ci
charset: utf8
columns:
name:
type: string(255)
attr_type:
type: integer(2)
label:
type: string(255)
sort_order:
type: integer(5)
default: 9999
relations:
CheItemAttribute:
local: id
foreign: attribute_id

CheItemAttribute:
options:
collate: utf8_unicode_ci
charset: utf8
columns:
item_id:
type: integer(12)
attr_value:
type: clob
attribute_id:
type: integer(12)
relations:
CheItem:
local: item_id
foreign: id
CheAttribute:
local: attribute_id
foreign: id

CheItemPhoto:
options:
collate: utf8_unicode_ci
charset: utf8
actAs:
Timestampable: ~
columns:
item_id:
type: integer(12)
basefile:
type: string(255)
caption:
type: string(255)
is_default:
type: boolean
default: false
relations:
CheItem:
local: item_id
foreign: id

fixtures.yml

CheAttribute:
Attr_price:
name: Price
label: price
sort_order: 1
attr_type: <?php echo CheAttribute::ATTR_STRING."\n" ?>
Attr_desc:
name: Desc
label: desc
sort_order: 2
attr_type: <?php echo CheAttribute::ATTR_HTML."\n" ?>

CheCategory:
Cat_0:
name: Items category
children:
Cat_1:
name: Cups
children:
Cat_2:
name: Beer
Cat_3:
name: Tea
children:
Cat_5:
name: China
Cat_6:
name: Russian
Cat_4:
name: Coffee

CheItem:
Item_8:
name: Vobla
CheCategory: Cat_1
Item_1:
name: Vobla2
CheCategory: Cat_2

CheItemAttribute:
Ite_attr_0:
CheItem: Item_1
CheAttribute: Attr_price
attr_value: 10
Ite_attr_1:
CheItem: Item_1
CheAttribute: Attr_desc
attr_value: abcsdd
Ite_attr_2:
CheItem: Item_8
CheAttribute: Attr_price
attr_value: 123
Ite_attr_3:
CheItem: Item_8
CheAttribute: Attr_desc
attr_value: test

code:

$b = Doctrine::getTable("CheAttribute")~~>createQuery("A2")~~>leftJoin("A2.CheItemAttribute IA2 WITH IA2.item_id = ?", 2)~~>addOrderBy("A2.sort_order ASC")~~>execute();

var_dump($b[0]~~>getCheItemAttribute()~~>getAttrValue());

$tb = Doctrine::getTable("CheAttribute")~~>createQuery("A")~~>leftJoin("A.CheItemAttribute IA WITH IA.item_id = ?", 1)~~>addOrderBy("A.sort_order ASC")~~>execute();

var_dump($tb[0]~~>getCheItemAttribute()~~>getAttrValue());
exit();

in browser i see:

string '10' (length=2)

but expected:

123

With hydration Array & Scalar hydrated data is ok.

[DC-430] I18n and inheritance

Fri, 15 Jan 2010 12:55:49 +0000

When using i18n with inheritance, the localizables fields are overrinden by the second deriving class.
So, the translation table is containing only fields from one of the two descending classes.

The yml is below:

User:
columns:
email: string(255)
...

Employer:
inheritance:
extends: User
type: column_aggregation
actAs:
I18n:
fields: [description, company]
columns:
company: string(255)
description: text

Recruiter:
actAs:
I18n:
fields: [position]
inheritance:
extends: User
type: column_aggregation
columns:
position: string(255)

[DC-432] ::isValidType fails when input format is different from php default format

Tue, 8 Jun 2010 16:55:41 +0000

In Validator::isValidType():
return (string)$var == strval(floatval($var));

floatval($var) returns only the integer part if the decimal character is anything other than ".".
Therefore this evaluation fails.

I've added a small function 'ParseFloat' which takes locale settings into consideration.
There might be a better solution.

[DC-436] Change in 1.2 to Doctrine_Event::skipOperation() functionality

Wed, 10 Feb 2010 06:02:18 +0000

I have been using Doctrine 1.1.6.

I have two related models, which are always saved together. In my application, save is called on class A and that save cascades to class B. I have a save listener which in some cases can intercept class A's save operation and call Doctrine_Event::skipOperation() to prevent class A from being persistently saved. However, in such cases, class B is still saved - the skipOperation() does not skip the entire operation, just class A's save operation, allowing subsequent operations to occur as normal.

This is the desired functionality and has been working fine. However, I have just upgraded to 1.2.1. only to find that something has changed, causing the skipOperation() to skip the entire operation, therefore not saving class B when class A's listener interferes.

I presume this is a bug. If not, what precisely has changed with skipOperation(), and how can I keep the traditional functionality?

[DC-438] Nesting Taggable and I18N

Tue, 19 Jan 2010 09:53:48 +0000

The Taggable extension doesnt work correctly when nested under I18N.
The page_translation_taggable_tag table appears to be correctly created, it has 3 columns: id, lang, tag_id
But when you save a tag like this
$page->Translation['en']->setTags('tag 1, tag2');
the lang column in page_translation_taggable_tag is empty
and this doesnt work either:
$page->setTags('tag 1, tag2');

Schema is this:
Page:
actAs:
I18n:
fields: [title, contents]
actAs:
Taggable: ~
columns:
title:

{type: string(255), notnull: true}

contents: clob

[DC-440] doctrine migration fails with taggable extension

Fri, 22 Jan 2010 11:18:02 +0000

When adding the Taggable behaviour to an entity, the doctrine migration fails (i'm using the symfony task) with the follwing error:

>> doctrine Migrating from version 0 to 1

The following errors occurred:

SQLSTATE[23000]: Integrity constraint violation: 1217 Cannot delete or update a parent row: a foreign key constraint fails. Failing Query: "DROP TABLE taggable_tag"

I have a single entity in my schema, with the Taggable behavior attached:

Article:
actAs:
Taggable: ~
columns:
title:

{ type: string(255), notnull: true }

body:

{ type: clob }

The Version1 class which was generate by the generate-migrations-diff task looks like this:

<?php
/**

This class has been auto-generated by the Doctrine ORM Framework
*/
class Version1 extends Doctrine_Migration_Base
{
public function up() { $this->dropTable('taggable_tag'); }

public function down()

{ $this->createTable('taggable_tag', array( 'id' => array( 'type' => 'integer', 'length' => '8', 'autoincrement' => '1', 'primary' => '1', ), 'name' => array( 'unique' => '1', 'type' => 'string', 'length' => '255', ), ), array( 'type' => '', 'indexes' => array( ), 'primary' => array( 0 => 'id', ), 'collate' => '', 'charset' => '', )); }

}

[DC-442] Refined definition of relations regarding "copy()" cloning behaviour

Wed, 10 Feb 2010 06:02:00 +0000

Doctrine's cloning feature is based on the Doctrine_Record::copy($deep = false) method, while the $deep param says whether to clone the related objects as well, or not.

However, considering the perspective of the application logic, the functional need can also be stated as: "I wish you to clone yourself, expecting you to know yourself which related objects you need to clone as well, or even to de-reference, or whatever is needed (e.g. to remove the relation)."
For this, the $deep argument is somehow inaccurate, as it does not take into consideration the different meanings of the relations:

some relations (namely aggregations in UML terminology) need that the cloned object shall still refer to the same object (like referenced by the cloned object)
some relations (namely compositions) need to clone the related objects as well, as the latter are owned by the main object.

Practical example: when cloning an invoice (Doctrine_Record), application logic expects that its invoice line items be cloned as well (compositions), but not the reference to the customer (cloning my customers this way will not increase my business .

Thus it would be great if there were a means to specify the needed behaviour in the schema.yml etc.
Thinkable approach: extend the "application-level cascade" feature of Doctrine by adding a "clone" or "copy" parameters. Then the copy() method in Doctrine_Record will know which related objects to clone as well, or not, or to clear (null). I guess it's quite analogous to the "delete" cascade stuff.

So far my proposal. In case it will find support, I will then be happy to provide an implementation proposal.

[DC-443] Incorrect insert order in i18n entities

Fri, 22 Jan 2010 11:29:13 +0000

If the schema has an entity MyMain with all its fields i18n and an entity MySecondary related to MyMain and you try to create a new MySecondary item using Symfony forms you get an error.

I think the error is doctrine and in i18n because if you remove a field from the i18n behavior (fields: [a,b,c,d], for example) all works ok.
I've included a symfony project to help developpers replicate the error.

My Schema

 
MyMain:
  actAs:
    I18n:
      fields: [a,b,c,d, e]
  columns:
    a:  { type: string(255), notnull: true }
    b:  { type: string(255), notnull: true }
    c:  string
    d:  string
    e:  string

MySecondary:
  columns:
    my_main_id:  integer
    a:        string(255)
    b:        string(255)
  relations:
    MyMain:
      local: my_main_id
      foreign: id
      foreignType: one
      cascade: [delete]

And the form code

class MyMainForm extends BaseMyMainForm
{
  public function configure()
  {
    $this->embedI18n(array('en', 'es'));
  }
}

class MySecondaryForm extends BaseMySecondaryForm
{
  public function configure()
  {
    $this->widgetSchema['my_main_id'] = new sfWidgetFormInputHidden();
    $this->embedRelation('MyMain as main_subform');
  }
}

And last the queries (and its order when you get the error)

INSERT INTO my_secondary (my_main_id, a, b) VALUES (?, ?, ?) - (, my_secondary[a], my_secondary[b])
INSERT INTO my_main_translation (id, lang, a, b, c, d, e) VALUES (?, ?, ?, ?, ?, ?, ?) - 
  (, en, my_secondary[main_subform][en][a], my_secondary[main_subform][en][b], my_secondary[main_subform][en][c], 
   my_secondary[main_subform][en][d], my_secondary[main_subform][en][e])
Error Doctrine_Connection_Mysql_Exception	SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'id' cannot be null

[DC-447] Problem linking many-to-many relationships

Mon, 25 Jan 2010 09:00:18 +0000

Hello,

Here's a small usage example of linking many-to-many relationships. The group is not linked with the user after calling link() as can be seen by comparing the group ids before and after the call.

schema.yml

User:
  tableName: users
  columns:
    username:      { type: string(255), notnull: true }
    email:         { type: string(255), notnull: true }
  indexes:
    username_idx:
      fields: [username]
      type:   unique
    email_idx:
      fields: [email]
      type:   unique
  actAs: [Timestampable]
  relations:
    groups:
      class:    Group
      alias:    Groups
      refClass: UserGroupRelation

Group:
  tableName: groups
  columns:
    name: { type: string(255), notnull: true }
  actAs: [Timestampable, NestedSet]
  relations:
    users:
      class:    User
      alias:    Users
      refClass: UserGroupRelation

UserGroupRelation:
  tableName: user_group_relations
  columns:
    user_id:  { type: integer, notnull: true, primary: true }
    group_id: { type: integer, notnull: true, primary: true }
  relations:
    Group:
      class:        Group
      foreignAlias: UserGroupRelations
      onDelete:     CASCADE
    User:
      class:        User
      foreignAlias: UserGroupRelations
      onDelete:     CASCADE

test.php

$u = Doctrine_Core::getTable('User')->findOneByUsername('james');
$g = Doctrine_Core::getTable('Group')->findOneByName('group');
var_dump($g['id']);
$current = array();
foreach ($u['UserGroupRelations'] as $r) {
    $current[] = $r['group_id'];
}
var_dump($current);
$u->link('Groups', array($g['id']), true);
$u = Doctrine_Core::getTable('User')->findOneByUsername('james');
$current = array();
foreach ($u['UserGroupRelations'] as $r) {
    $current[] = $r['group_id'];
}
var_dump($current);

Output

string(1) "2"
array(3) {
  [0]=>
  string(1) "1"
  [1]=>
  string(1) "5"
  [2]=>
  string(1) "6"
}
array(3) {
  [0]=>
  string(1) "1"
  [1]=>
  string(1) "5"
  [2]=>
  string(1) "6"
}

[DC-449] Duplicate entry integrity constraint error when updating Searchable record with indexed fields from a template

Mon, 25 Jan 2010 10:58:24 +0000

I have the following:

<?php
class JS_Page extends Doctrine_Record
{
	public function setTableDefinition()
	{
		$this->setTableName('page');
		$this->hasColumns(array(
			'id' => array(
				'type'		=> 'integer',
				'length'	=> 4,
				'primary'	=> true,
				'autoincrement'	=> true,
			),
			'content' => array(
				'type'		=> 'array',
				'length'	=> 65536,
				'notnull'	=> true,
				'default'	=> array(),
			),
		));
	}

	public function setUp()
	{
		$this->actAs(new JS_Template_Meta());
		$this->actAs('Searchable', array(
			'fields'	=> array('title', 'description', 'keywords'),
			'tableName'	=> 'page_index',
		));
	}
}

class JS_Template_Meta extends Doctrine_Template
{
	public function setTableDefinition()
	{
		$this->hasColumns(array(
			'title' => array(
				'type'		=> 'string',
				'length'	=> 255,
				'notnull'	=> true,
			),
			'description' => array(
				'type'		=> 'string',
			),
			'keywords' => array(
				'type'		=> 'string',
				'length'	=> 255,
			),
		));
	}
}

When a Page record is updated I get this error:

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'application-title-0-3' for key 1

If I only index fields from Page it works.

I tracked this down to the code in Doctrine_Search that deletes the existing indexed data before re-indexing a record (I'm not using batchUpdate). For reasons I don't understand the DELETE query is not executing correctly before re-indexing, and so any unchanged data is being added to the index twice, causing the error.

I managed to work around this by adding my own template and listener before Searchable, with a preSave event that deletes the index data:

...
		$this->actAs(new JS_Template_Searchable());
		$this->actAs('Searchable', array(
			'fields'	=> array('title', 'description', 'keywords'),
			'tableName'	=> 'page_index',
		));
...

class JS_Template_Searchable extends Doctrine_Template
{
	public function setTableDefinition()
	{
		$this->addListener(new JS_Template_Searchable_Listener());
	}
}

class JS_Template_Searchable_Listener extends Doctrine_Record_Listener
{
	public function preSave(Doctrine_Event $event)
	{
		$invoker = $event->getInvoker();
		$class = get_class($invoker) . 'Index';
		$query = Doctrine_Query::create()
			->delete()
			->from("{$class} i")
			->where("i.id = ?", $invoker['id'])
			->execute();
	}
}

Obviously that's an ugly hack, but it works.

[DC-450] ORACLE: The generate DQL with i18n behavior doesn't correct

Thu, 18 Mar 2010 06:54:44 +0000

My schema:

---
Country:
  tableName:          country
  actAs:
    SoftDelete:       ~
    Timestampable:    ~
    I18n:
      fields:         [name]
      className:      %CLASS%I18n
      tableName:      %TABLE%_i18n
      length:         5
  columns:
    id:
      type:           integer(3)
      primary:        true
      unsigned:       true
      sequence:       country
    created_at:
      type:           timestamp
    updated_at:
      type:           timestamp
    enabled_at:
      type:           timestamp
      notnull:        true
    disabled_at:
      type:           timestamp
    iso_code:
      type:           string(2)
    marc_code:
      type:           string(3)
    name:
      type:           string(255)
      notnull:        true

DQL query:

 
$country = Doctrine::getTable('Country')->findOneByMarcCode('sz');

Error:

 
ORA-00904: "C"."NAME": invalid identifier : SELECT a.* FROM ( SELECT c.id AS c__id, c.created_at AS c__created_at, c.updated_at AS c__updated_at, c.enabled_at AS 
c__enabled_at, c.disabled_at AS c__disabled_at, c.iso_code AS c__iso_code, c.marc_code AS c__marc_code, c.name AS c__name, c.deleted_at AS c__deleted_at FROM
common.country c WHERE (c.marc_code = :oci_b_var_1) ) a WHERE ROWNUM <= 1

In this line, i show the field "name", but this field is in table translation. The DQL above is very complicated for only simple request. Why ?

Thank's

Bertrand

[DC-451] preDql events on connection & manager level

Mon, 25 Jan 2010 14:08:30 +0000

I think it would be very helpful if the preDql events also worked on connection and manager level. If it is anyway possible.

attach a record listener to a connection object, and it should also call the preDql events when doing DQL queries.

[DC-453] Joined records stated as dirty (whereas they are not modified)

Thu, 29 Jul 2010 15:58:54 +0000

When you retrieve records like this:

(Here I have Labels, that have Albums)

$lab = Doctrine::getTable('Label')->createQuery('lab')
->leftJoin('lab.Albums alb')
->select('lab.id, alb.id')
->where('lab.id = ?', 1)
->fetchOne();

$lab->state() is STATE_PROXY : it's ok, properties are not all loaded from the DB and the object is not modified

BUT $lab->Albums[0]->state() is STATE_DIRTY : why ? the object is not modified...

This causes real problems, because this way, joined objects unloaded properties are corrupted : it really behaves like they all are "null", and that's all. Their real values are never loaded from the DB.

[DC-467] Can't create root node if multiple roots and primary key have multiple columns

Fri, 16 Apr 2010 12:17:22 +0000

When trying to create new root node, the following exception is thrown.

PHP Fatal error: Uncaught exception 'Doctrine_Tree_Exception' with message 'Node must have a root id set or must be persistent and have a single-valued numeric primary key in order to be created as a root node. Automatic assignment of a root id on transient/new records is no longer supported.'

This only happens when hasManyRoots is true, and table have multiple columns in primary key.

Example:

$category = new Menu();
$category->name = 'Menu Root';
$category->language_id = 1;
$category->root_id = 23;
$category->save();

$treeObject = Doctrine::getTable('Menu')->getTree();
$treeObject->createRoot($category);

and menu table is defined as follows:

$this->hasColumn('id', 'integer', 8, array(
'type' => 'integer',
'primary' => true,
'autoincrement' => true,
'length' => '8',
));
$this->hasColumn('language_id', 'integer', 8, array(
'type' => 'integer',
'primary' => true,
'length' => '8',
));

If i remove primary option from language_id column, everything works as it should.

[DC-473] createIndexSql() and dropIndexSql() use different index names (formatter) on MySQL and Postgres

Tue, 8 Jun 2010 17:04:37 +0000

While playing with createIndexSql() and dropIndexSql() i noticed, that the pgsql implementation differs from mysql. The index names usually are build with a '_idx' after the name. This is done through the formatter, i guess.

I noticed, that in Doctrine_Export class the createIndexSql() method does not use the formatter, while dropIndexSql() do. So creating and dropping indexes on pgsql (in my case) fails because of the different names. It does work on mysql, because Doctrine_Export_Mysql class uses it's own createIndexSql() method where the formatter is used.

Michael

[DC-476] PHP's is_subclass_of function causing failure in some contexts

Fri, 30 Apr 2010 11:04:48 +0000

I have a suspicion that this is related to issue: DC-386

The bug manifested its-self by bailing with no php error output when calling Doctrine_Pager::execute() in php 5.2.10 (5.3 appears to work - Mac OS X while 5.2.10 fail on ubuntu and centos).

I traced this down to Doctrine_Record::processPendingFields(), the offending line number is #477.

Interestingly, if I call is_subclass_of() with exactly the same params in my view just prior to calling Doctrine_Pager::execute() in my code, the error does not present its-self , i.e. I'b adding the following code :

is_subclass_of('Doctrine_Hydrator_RecordDriver', 'Doctrine_Hydrator_Graph');

It can also be avoided by calling Doctrine_Pager::getQuery()->getQuerySql(); and no doubt other code paths which change the environment in some way.

[DC-478] Having a default value in a decimal field in base class forces Doctrine to try to save an instance even if not required.

Thu, 4 Feb 2010 09:49:13 +0000

I have 2 classes. Order and Branch. An Order class can have one or no branch assigned to it. My base class definition for a branch is simple. It just has a name.

The Order class has:
$this->hasColumn('branchId', 'integer');

and

$this->hasOne(
'Fds_Model_Branch as branch',
array(
'local' => 'branchId',
'foreign' => 'id',
)
);

The branch class had this:

$this->hasColumn('name', 'string', 50, array(
'notnull' => true,
'notblank' => true,
));

No hasMany relation back to Orders.

Using this setup, all my tests work.

I added this to the Branch class.
$this->hasColumn(
'localTax', 'decimal', null,
array(
'notnull' => true,
'default' => 0,
)
);

Now my tests fail with a validator error from the branch class for the name property whenever I try to save an order that has no branch associated to it. Pretty weird right? I mean, my order has no branch, and yet Doctrine tries to save one.

But if I change the definition of localTax to this:
$this->hasColumn('localTax', 'decimal');

Then my tests work as expected again. Problem is, I need to assign the default value of 0 to localTax instead of null.

Is this a bug?

[DC-485] Limit gets lost when doing self join

Mon, 8 Feb 2010 11:06:41 +0000

hi doctrine team,
today I encountered a very weird problem when I tried to do a selfjoin on a table. the goal was to list all people that have the same addresses but limit the result to 5

the problem was, that the doctrine split it into 2 querys and first selected the correct address ids with the Limit 5. but in the second query the limit is lost. which gives me more than 5 results if a few people have the same address

the DQL looks like this

$q = DQ::create()
->from('address a INNER JOIN a.shared b ON a.city = b.city AND a.street = b.street')
->innerJoin('b.entity e')
->where('a.entity_id = ? AND a.is_active = ?', array($id, $is_active))
->limit(5)
->offset(0);

SQL looks like this:

SELECT * FROM address a
INNER JOIN address a2 ON ((a.city = a2.city AND a.street = a2.street))
INNER JOIN entity e ON a2.entity_id = e.id
WHERE a.id IN ('5689677') AND (a.entity_id = ? AND a.is_active = ?)

Problem: Limit 5 is gone

expected was something like this:

SELECT *
FROM address a
INNER JOIN address b ON a.city = b.city AND a.street = b.street
INNER JOIN entity e ON b.entity_id = e.id
where a.entity_id = 104294414
limit 5

my temporary solution:

$q = new Doctrine_RawSql();
$q->select('

{b.*}

{e.*}

{p.*}

');
$q->from('address a INNER JOIN address b ON a.city = b.city AND a.street = b.street
INNER JOIN entity e ON b.entity_id = e.id
INNER JOIN person p ON e.id = p.entity_id');
$q->where('a.entity_id = ? AND a.is_active = ?', array($id, $isActive));
$q->addComponent('a', 'address a');
$q->addComponent('b', 'a.shared b');
$q->addComponent('e', 'b.entity e');
$q->addComponent('p', 'e.person p');
$q->limit($limit);
$q->offset($offset);

my schema.yml is attached, do you need anything else?

[DC-486] Taggable extension bound to inherited class also binds to all classes, which extend the base one

Mon, 8 Feb 2010 12:54:40 +0000

This is my schema.yml:

Tale:
actAs:
Taggable:
columns: # there are some not interesting columns

FolkTale:
inheritance:
extends: Tale
type: column_aggregation
keyField: type
keyValue: folk
columns:
folk_id: integer
relations:
Folk:
class: Folk
local: folk_id
foreign: id
type: one
onDelete: CASCADE

AuthoredTale:
inheritance:
extends: Tale
type: column_aggregation
keyField: type
keyValue: authored
columns:
author_id: integer
relations:
Author:
class: Author
local: author_id
foreign: id
type: one
onDelete: CASCADE

When I do ./symfony doctrine:build --all I see three *_taggable_tag table in my DB (folk_tale_taggable_tag, authored_tale_taggable_tag and tale_tag) instead of expected one tale_tag.

[DC-496] Doctrine should warn when a columns / table name match a reserved word

Fri, 12 Feb 2010 13:58:37 +0000

Today i looked for quite a long time why doctrine doesn't acte like i wish...

it turns out that it was because of a column named 'system_id'... doctrine use this for internal use.

no pbm with that, but please notify users that they will experience pbm when a column or table name match X or Y or Z.

i've experienced pbm with : table_name, system_id, and some other id too.

[DC-499] Doctrine_Query_Set incorrectly rewrites expressions

Fri, 4 Feb 2011 13:38:04 +0000

First up Doctrine_Query_Set should extend Doctrine_Query_Condition so that the parseLiteralValue method is available in _processPossibleAggExpression().

However I am not sure what this method is really supposed to do. It seems to do some reordering of clauses, but in my case it actually drops off some parts of my expression:
Doctrine_Query::create()
->update('Document')
->set('clause_ordering', "IF(clause_ordering IS NULL, '$id', CONCAT(clause_ordering, ',$id'))")
->where('id = ?', $document_id)
->execute();

Results in "UPDATE document SET clause_ordering = IF(clause_ordering IS NULL, '67', CONCAT(clause_ordering)) WHERE (id = ?)"

And not as expected "UPDATE document SET clause_ordering = IF(clause_ordering IS NULL, '67', CONCAT(clause_ordering, ',67')) WHERE (id = ?)"

Adding a space after IF and CONCAT fixes the issue, but is obviously a hack to get around the regexp in _processPossibleAggExpression()

[DC-501] Join and WITH keywords : documentation is confusing

Mon, 15 Feb 2010 12:28:15 +0000

Your documentation makes no sense to me on the usage of the WITH keyword

http://www.doctrine-project.org/documentation/manual/1_1/en/dql-doctrine-query-language:join-syntax#with-keyword

$q = Doctrine_Query::create()
  ->select('u.id, p.id')
  ->from('User u')
  ->leftJoin('u.Phonenumbers p WITH u.id = 2');

Get Users and the phone numbers if any of the user 2 (we could indeed need that kind of query)

-----------------------------------------------------------------------------------------------------------------------------------
I guess this kind of example query is better

// Documentation
Get users and their mobile phone numbers if any

$q = Doctrine_Query::create()
  ->select('u.id, p.id')
  ->from('User u')
  ->leftJoin('u.Phonenumbers p WITH p.type = ?', 'mobile');

you can expect this SQL

SELECT 
u.id AS u__id, 
p.id AS p__id 
FROM User u 
LEFT JOIN Phonenumbers p ON u.id = p.user_id AND p.type = 'mobile'

// Still in the documentation
Be aware that this query is different of

$q = Doctrine_Query::create()
  ->select('u.id, p.id')
  ->from('User u')
  ->leftJoin('u.Phonenumbers p')
  ->where('p.type = ?', 'mobile')
;

because you will strip away the users who do not have a mobile phone number

-----------------
Also the second example is more confusing ...

$q = Doctrine_Query::create()
    ->select('u.id')
    ->from('User u')
    ->leftJoin('u.Groups g')
    ->innerJoin('u.Phonenumbers p WITH u.id > 3')
    ->leftJoin('u.Email e');

Means : Get Users (who HAVE Phonenumbers (innerJoin)) with their potential (leftJoin) Groups, potential (leftJoin) Emails, and their Phonenumbers
but not for the Users 1, 2 and 3

Not really the straight forward example we can expect in a documentation

Best regards

[DC-502] sometimes not all the constraints are created for a many to many relation

Mon, 14 Jun 2010 03:38:30 +0000

it seems that the naming is important:

in a User, Group, UserGroup relation (where the UserGroup defines the many to many relation for User & Group) the constraints are defined well

but if the tables are Order, Service, OrderService it doesn't work => just one constraint is created... please find my example:

schema.yml

Order:
  tableName:          orders
  columns:
    name:             string(50)
  relations:
    Services:
      class:          Service
      local:          order_id
      foreign:        service_id
      refClass:       OrderService

Service:
  actAs:
    Versionable:      ~
  columns:
    name:             string(50)
  relations:
    Orders:
      class:          Order
      local:          service_id
      foreign:        order_id
      refClass:       OrderService

# WTF: it takes alphbetically the constraints building  !?
# if I used ZorderService instead of OrderService, Z is after S (O is before S) the constraints are defined fine!
OrderService:
  columns:
    order_id:         { type: integer, primary: true }
    service_id:       { type: integer, primary: true }

==> the generated SQL

sql

CREATE TABLE orders (id BIGINT AUTO_INCREMENT, name VARCHAR(50), PRIMARY KEY(id)) ENGINE = INNODB;
CREATE TABLE order_service (order_id BIGINT, service_id BIGINT, version BIGINT, PRIMARY KEY(order_id, service_id, 
        version)) ENGINE = INNODB;
CREATE TABLE service_version (id BIGINT, name VARCHAR(50), version BIGINT, PRIMARY KEY(id, version)) ENGINE = 
        INNODB;
CREATE TABLE service (id BIGINT AUTO_INCREMENT, name VARCHAR(50), version BIGINT, PRIMARY KEY(id)) ENGINE = 
        INNODB;
ALTER TABLE order_service ADD CONSTRAINT order_service_order_id_orders_id FOREIGN KEY (order_id) REFERENCES 
        orders(id);
ALTER TABLE service_version ADD CONSTRAINT service_version_id_service_id FOREIGN KEY (id) REFERENCES service(id) 
        ON UPDATE CASCADE ON DELETE CASCADE;

=> as you can see for TABLE order_service just one constraint is defined (order_service_order_id_orders_id) the other one (order_service_service_id_service_id) is missing !!!

However if i change the names for tables (actually i think alphabetically order) and use ZorderService instead of OrderService (lik UserGroup for User & Group) the two constraints are created!

This also affects the "getRelations()" when i tried to write a behavior (it gives back just one relation):

  foreach ($event->getInvoker()->getTable()->getRelations() as $relation)

ps:
also the same bug reported on the list: http://groups.google.com/group/doctrine-user/browse_thread/thread/ad48db71b71e043b

_{(edit G.X: split too long lines in SQL code)}

[DC-509] Oracle don't close cursor

Thu, 28 Jul 2011 16:18:46 +0000

When you doing a big loop of insertion you have a "too many open cursor".
The problem is in Doctrine_Connection class
At line 1005 you should replace :
$stmt = $this->prepare($query);
by
$stmt = $this->dbh->prepare($query);

and at line 1041 you should replace :
$stmt = $this->prepare($query);
by
$stmt = $this->dbh->prepare($query);

After this correction, you never have the problem "too many open cursor"

Thanks to Ota to point that on google groups.
http://groups.google.com/group/doctrine-user/browse_thread/thread/fe6cd03c8fb18b64/728ec1b4e42b1f0b?lnk=gst&q=doctrine_oracle_adapter#728ec1b4e42b1f0b

[DC-519] ->where() add parentheses

Tue, 23 Feb 2010 12:51:49 +0000

I have this method

public function getOpenBalances()

{ $q = $this->createQuery('a') ->select('a.*') ->where('a.invoice_id IN ( SELECT ac.invoice_id FROM AccountingCustomers ac GROUP BY ac.invoice_id HAVING (SUM(ac.dedit) - SUM(ac.credit)) > 0)'); return $q->execute(); }

and yhis is the error generated in symfony:

SQLSTATE[42601]: Syntax error: 7 ERROR: syntax error at or near ")" at character 456. Failing Query: "SELECT a.id AS a_id, a.customer_id AS acustomer_id, a.invoice_id AS ainvoice_id, a.credit AS acredit, a.duedate AS aduedate, a.debit AS adebit, a.paymentdate AS apaymentdate, a.note AS anote, a.created_at AS acreated_at, a.updated_at AS aupdated_at FROM accounting_customers a WHERE (a.invoice_id IN (SELECT a2.invoice_id AS a2_invoice_id FROM accounting_customers a2 GROUP BY a2.invoice_id HAVING (SUM(ac.dedit) - SUM(a2.credi))) > 0))"

At the end ther is a parentheses that the code haven't. ))) > 0))

and another problem is that SUM(ac.credit) is changed in SUM(a2.credi)

[DC-526] Savepoint-rollback ignored in nested transaction context.

Fri, 6 Aug 2010 03:11:39 +0000

The example from the documentation on savepoints:

 
try {
    $conn->beginTransaction();
    // do some operations here 

    // creates a new savepoint called mysavepoint
    $conn->beginTransaction('mysavepoint');
    try {
        // do some operations here

        $conn->commit('mysavepoint');
    } catch(Exception $e) {
        $conn->rollback('mysavepoint'); # (a)
    }
    $conn->commit();
} catch(Exception $e) {
    $conn->rollback();
}

What seems to be a bug to me: (a) doesn't actually do a savepoint-rollback if reached, but rather returns false as soon as the nesting level is seen to be > 1.

[DC-536] Duplicate CREATE TABLE entries in schema.sql when using column_inheritance

Thu, 18 Nov 2010 01:44:16 +0000

When creating a model involving column_inheritance the CREATE TABLE statement gets duplicated.

The second CREATE TABLE include an index for the keyField.

Test doctrine generated models and generated schema.sql attached.

[DC-541] MSSQL Server: Enabling MARS prevents the saving of records.

Thu, 10 Jun 2010 04:40:57 +0000

This is related to issue #540. In order to circumvent that issue, I enabled MARS (Multiple Active Result Sets) - now when attempting to save any record the following error results:

Fatal error: Uncaught exception 'Doctrine_Transaction_Exception' with message 'Rollback failed. There is no active transaction.' in C:\www\doctrine\lib\Doctrine\Transaction.php on line 319

This is actually caused by the following MSSQL error:

exception 'Doctrine_Transaction_Exception' with message 'SQLSTATE[42000]: Syntax error or access violation: 3997 [Microsoft][SQL Server Native Client 10.0][SQL Server]A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back. (SQLExecDirect[3997] at ext\pdo_odbc\odbc_driver.c:247)' in C:\www\doctrine\lib\Doctrine\Transaction.php:212 Stack trace: #0 C:\www\doctrine\lib\Doctrine\Transaction.php(511): Doctrine_Transaction->beginTransaction(NULL) #1 C:\www\doctrine\lib\Doctrine\Connection.php(1377): Doctrine_Transaction->beginInternalTransaction(NULL) #2 C:\www\doctrine\lib\Doctrine\Connection\UnitOfWork.php(64): Doctrine_Connection->beginInternalTransaction() #3 C:\www\doctrine\lib\Doctrine\Record.php(1691): Doctrine_Connection_UnitOfWork->saveGraph(Object(Model)) #4 C:\www\doctrine\tools\sandbox\index.php(83): Doctrine_Record->save() #5

{main}

I haven't worked out what's going on yet, but this blog post may shed some light on it:
http://blogs.msdn.com/cbiyikoglu/archive/2006/11/21/mars-transactions-and-sql-error-3997-3988-or-3983.aspx

I've attached a script to reproduce this issue in the sandbox (MARS is enabled in the DSN).

[DC-544] Doctrine_Pager bug with Oracle. getNumResults doesn't return the correct number of records

Thu, 18 Mar 2010 08:02:39 +0000

The function getNumResults() doesn't work correctly.

This is my model class

class ReviewListTable extends Doctrine_Table
{
 public function getAvailable()
 {
   return $this->createQuery()
   ->select('DISTINCT(to_char(file_date, \'YYYY-MM-DD\')) fdate')
   ->orderBy('fdate DESC');
 }
}

If i execute this fonction, the number of record is 31. If i use the Pager, the result is 5744 records

Controler:

$this->pager = new Doctrine_Pager(
                           Doctrine_Core::getTable('ReviewList')->getAvailable(),
                           $request->getParameter('page', 1),
                           20);

View:

$rs = $this->pager->execute();
echo $pager->getNumResults();

[DC-553] issue when changing the connection inside Doctrine_Query::preQuery() on a model using a behavior

Mon, 19 Jul 2010 07:45:41 +0000

We were following:
http://www.doctrine-project.org/documentation/cookbook/1_1/en/master-and-slave-connections

class MyQuery extends Doctrine_Query
{
// Since php doesn't support late static binding in 5.2 we need to override
// this method to instantiate a new MyQuery instead of Doctrine_Query
public static function create($conn = null)

{ return new MyQuery($conn); }

public function preQuery()
{
// If this is a select query then set connection to one of the slaves
if ($this->getType() == Doctrine_Query::SELECT)

{ $this->_conn = Doctrine_Manager::getInstance()->getConnection('slave_' . rand(1, 4)); // All other queries are writes so they need to go to the master }

else

{ $this->_conn = Doctrine_Manager::getInstance()->getConnection('master'); }

}
}

However we are actually forcing all queries after the first access to the master to be run against the master (including selects). Note the example should probably be changed to use setConnection(). However even when using setConnection() it seems like changing the connection can cause issues when running a select on a model with a behavior (in our case we were using i18n). Therefore we believe there is some issue that is caused through the event system, because otherwise queries work just fine even when changing the connection as per the above described code.

We managed to fix things, by not setting the connection explicitly and instead simply using setCurrentConnection('master'), so the bug does not affect us anymore. However this seems to indicate some issues deep inside the event-behavior-template code.

[DC-554] Distinct query does not work

Mon, 15 Mar 2010 16:11:04 +0000

$limit = 10;
$q = 'Me';
$field = 'contractor';

$q = Doctrine_Query::create()
->select(sprintf('DISTINCT PublicContract.%s', $field))
->from('PublicContract')
->where(sprintf('PublicContract.%s LIKE ?', $field), sprintf('%%%s%%', $q))
->limit($limit);

The QUERY is WRONG:

// SELECT DISTINCT p.id AS p_id, p.contractor AS p_contractor FROM public_contract p WHERE (p.contractor LIKE ?) LIMIT 10 - (%Me%)

I can simply GROUP BY the contractor field, because DISTINCT can be considered as a special case of GROUP BY - and have the results I want:

$q = Doctrine_Query::create()
->select(sprintf('PublicContract.%s', $field))
->from('PublicContract')
->where(sprintf('PublicContract.%s LIKE ?', $field), sprintf('%%%s%%', $q))
->groupBy(sprintf('PublicContract.%s', $field))
->limit($limit);

[DC-575] Select distinct limit problem

Wed, 30 Jun 2010 02:57:45 +0000

1)Code
Doctrine_Query::create ()
->select ( "u.user_id,mr.message_id,mr.message_senddate,mr.message_title,mr.message_content,mr.message_alias,mr.message_categoryid," )
->from ( "user u" )
->leftJoin ( "u.messages mr ON u.user_id = mr.message_sender" )
->where ( "u.user_id = ?", 2 )
->limit(1)
->fetchArray ();

This code must return only one result but it returns all results in which user_id is 2 in the database

If i looked it in Symfony Debug bar, i saw that;

2)Symfony debug toolbar values:

#Query A
SELECT DISTINCT u2.user_id FROM users u2 LEFT JOIN messages m2 ON (u2.user_id = m2.message_sender) WHERE u2.user_id = 2 LIMIT 1

#Query B
SELECT u.user_id AS u_user_id, m.message_id AS mmessage_id, m.message_senddate AS mmessage_senddate, m.message_title AS mmessage_title, m.message_content AS mmessage_content, m.message_alias AS mmessage_alias, m.message_categoryid AS m_message_categoryid FROM users u LEFT JOIN messages m ON (u.user_id = m.message_sender) WHERE u.user_id IN ('2') AND (u.user_id = 2)

And if i test this code in MYSQL query browser i got a result like that;

SELECT u.user_id AS u_user_id, m.message_id AS mmessage_id, m.message_senddate AS mmessage_senddate, m.message_title AS mmessage_title, m.message_content AS mmessage_content, m.message_alias AS mmessage_alias, m.message_categoryid AS m_message_categoryid
FROM users u
LEFT JOIN messages m ON ( u.user_id = m.message_sender )
WHERE u.user_id
IN (
'2'
)
AND (
u.user_id =2
)
LIMIT 0 , 30

If i changed SQL code like below and put the limit at end, the problem solved:

#Query A
SELECT DISTINCT u2.user_id FROM users u2 LEFT JOIN messages m2 ON (u2.user_id = m2.message_sender) WHERE u2.user_id = 2

But doctrine's limit(1) metod is Select Distinct

The query which starts with ... is at query A but it needs to be at the end of query B

[DC-581] ORACLE: Missing fields on subquery with Many:Many

Thu, 18 Mar 2010 06:09:27 +0000

I use this schema:

---
Actuality:
  connection:         web
  tableName:          actuality
  actAs:
    softDelete:       ~
    Timestampable:    ~
    Sluggable:
      fields:         [name]
      indexName:      actuality_sluggable
      canUpdate:      true
  columns:
    id:
      type:           integer(4)
      primary:        true
      unsigned:       true
      sequence:       actuality
    created_at:
      type:           timestamp
    updated_at:
      type:           timestamp
    published_at:
      type:           timestamp
      notnull:        true
    unpublished_at:
      type:           timestamp
    name:
      type:           string(255)
      notnull:        true
    description_short:
      type:           string(1000)
      notnull:        true
    description:
      type:           clob
      notnull:        true
    is_professional:
      type:           boolean
      default:        true
  relations:
    Categories:
      class: ActualityCategory
      local: actuality_id
      foreign: actuality_category_id
      refClass: ActualityActualityCategory
      foreignAlias: Actualities


ActualityActualityCategory:
  connection:         web
  tableName:          actuality_actuality_category
  options:
    symfony:
      form:   false
      filter: false
  columns:
    actuality_id:
      type:           integer(4)
      primary:        true
      unsigned:       true
    actuality_category_id:
      type:           integer(2)
      primary:        true
      unsigned:       true
  relations:
    Actuality:
      onDelete:       CASCADE
    

ActualityCategory:
  connection:         web
  tableName:          actuality_category
  actAs:
    softDelete:       ~
    Timestampable:    ~
    Sluggable:
      fields:         [name]
      indexName:      actualityc_sluggable
      canUpdate:      true
  columns:
    id:
      type:           integer(2)
      primary:        true
      unsigned:       true
      sequence:       actualitycategory
    created_at:
      type:           timestamp
    updated_at:
      type:           timestamp
    name:
      type:           string(60)
      notnull:        true

Function in my model Actuality

public function retrieveActive($is_authenticated = false)
{
  $q = $this->createQuery('a')
  ->leftJoin('a.Categories c')
  ->orderBy('a.published_at DESC');
  
  if (!$is_authenticated)
  {
    $q->where('a.is_professional = ?', false);
  }
  
  return $q;
}

with that, i receive the message "Doctrine_Connection_Oracle_Exception" because Oracle is strict and in the subselect, the field published_at is missing in select. This is the query generate by doctrine:

SELECT a.id AS a__id, a.published_at AS a__published_at, a.name AS a__name, a.description_short AS a__description_short, a.slug AS a__slug, a2.id AS a2__id, a2.name AS a2__name FROM actuality a LEFT JOIN actuality_actuality_category a3 ON (a.id = a3.actuality_id) LEFT JOIN actuality_category a2 ON a2.id = a3.actuality_category_id WHERE a.id IN (SELECT a4.id FROM ( SELECT DISTINCT a4.id FROM actuality a4 LEFT JOIN actuality_actuality_category a6 ON (a4.id = a6.actuality_id) LEFT JOIN actuality_category a5 ON a5.id = a6.actuality_category_id WHERE a4.is_professional = 0 ORDER BY a4.published_at DESC ) a4 WHERE ROWNUM <= 5) AND (a.is_professional = 0) ORDER BY a.published_at DESC

If i execute this query and add the field published_at in subquery, this is work.

SELECT a.id AS a__id, a.published_at AS a__published_at, a.name AS a__name, a.description_short AS a__description_short, a.slug AS a__slug, a2.id AS a2__id, a2.name AS a2__name FROM actuality a LEFT JOIN actuality_actuality_category a3 ON (a.id = a3.actuality_id) LEFT JOIN actuality_category a2 ON a2.id = a3.actuality_category_id WHERE a.id IN (SELECT a4.id FROM ( SELECT DISTINCT a4.id, a4.published_at  FROM actuality a4 LEFT JOIN actuality_actuality_category a6 ON (a4.id = a6.actuality_id) LEFT JOIN actuality_category a5 ON a5.id = a6.actuality_category_id WHERE a4.is_professional = 0 ORDER BY a4.published_at DESC ) a4 WHERE ROWNUM <= 5) AND (a.is_professional = 0) ORDER BY a.published_at DESC

Thanks for your help.

[DC-585] Hydrate Array does not return full array, when Hydrate Scalar does

Fri, 2 Mar 2012 17:44:46 +0000

Description : Upon hydrating as array I will receive one row returned. If I am to hydrate as Scalar, I will get 200+ rows. Also, if i echo the sql ($q->getSqlQuery()) and run that raw, it will also return around 200+ rows.

$q = Doctrine_Query::create()
->select('DISTINCT(co.name) AS field, co.name AS value')
->from('Model_Country co')
->leftJoin('co.City ci');

//here we will get only the first row
$results = $q->execute(array(), Doctrine::HYDRATE_ARRAY);

//Here we will get all 200+ rows
$results = $q->execute(array(), Doctrine::HYDRATE_SCALAR);

I have yet to dig to deep into this, but if it is indeed a bug, my guess is it is in Doctrine_Hydrator_Graph::hydrateResultSet()

I can provide more data if needed.

[DC-587] Problem with non equal self referencing many to many relations

Tue, 8 Jun 2010 16:18:20 +0000

I think that this bug has been reported already here:
http://www.doctrine-project.org/jira/browse/DC-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
But I thought that it might be useful to submit a very simple test case, with the bug completely isolated.
When you create a self referenced non equal many-to-many relation like: person has many parents AND has many children (taken from the documentation).

In the attached test case, after both collections of related records are altered within the foreach statement, Doctrine somehow messes up the Ids in the reference class. Now, it's important to note, that if you loop through just one of the collections, it won't fail.

Thanks in advance!

[DC-589] refreshRelated() causes an id to be changed from string to int, causing an unnecessary update query.

Mon, 29 Mar 2010 14:51:08 +0000

Here is an example:

class Article extends Doctrine_Record
{
    public function setTableDefinition()
    {
        $this->hasColumn('title', 'string', 255);
        $this->hasColumn('body', 'string', 4096);
    }

    public function setUp()
    {
        $this->hasMany('Comment as Comments', array(
            'local' => 'id',
            'foreign' => 'articleId',
        ));
    }
}

class Comment extends Doctrine_Record
{
    public function setTableDefinition()
    {
        $this->hasColumn('comment', 'string', 4096);
        $this->hasColumn('articleId', 'integer');
    }

    public function setUp()
    {
        $this->hasOne('Article', array(
            'local' => 'articleId',
            'foreign' => 'id',
        ));
    }

    public function preUpdate($e)
    {
        throw new Exception('should not get here');
    }

}

$a = new Article();
$a->title = 'Hi';
$a->body = 'There';
$a->save();

$c = new Comment();
$c->comment = '1st comment';
$c->articleId = $a->id;
$c->save();

$a->refreshRelated('Comments');

$a->title = 'Hello';
$a->save();

What happens above is that the call to refreshRelated() causes the 'id' of the comment to change from string:1 to int:1, which causes the last save of the article to try to save the comment. The exception is there just to illustrate that the Comment is being updated (which should not happen). For us - this is an issue not just because of the extra query, but because some entities in the system (like log entries) actually throw when updated.

Tested against latest trunk.

The issue seems to be introduced in r7361.

[DC-595] Array hydration fails when sorting DESC

Tue, 23 Mar 2010 06:12:53 +0000

Wrong array hydration results.

Running toArray() on non hydrated collection
produces different results than using array hydrator.

Case1.
Sorting ASC (works)

$reputationHydrated = Doctrine_Query::create()
->from('User_Model_UserReputation ur')
->leftJoin('ur.User u')
->leftJoin('ur.Thread t')
->leftJoin('t.ForumEntry fe')
->where('u.id = ?', 1)
->orderBy('ur.event ASC)
->execute(null, Doctrine_Core::HYDRATE_ARRAY);

$reputation = Doctrine_Query::create()
->from('User_Model_UserReputation ur')
->leftJoin('ur.User u')
->leftJoin('ur.Thread t')
->leftJoin('t.ForumEntry fe')
->where('u.id = ?', 1)
->orderBy('ur.event ASC)
->execute();

$reputationToArray = $reputation->toArray();

die($reputationToArray === $reputationHydrated); // true, as expected

Case 2.
Sorting DESC (does not work)

$reputationHydrated = Doctrine_Query::create()
->from('User_Model_UserReputation ur')
->leftJoin('ur.User u')
->leftJoin('ur.Thread t')
->leftJoin('t.ForumEntry fe')
->where('u.id = ?', 1)
->orderBy('ur.event DESC)
->execute(null, Doctrine_Core::HYDRATE_ARRAY);

$reputationToArray = $reputation->toArray();

die($reputationToArray === $reputationHydrated); // false, should be true

Other hydrators do hydrate as expected.

Seems that something is wrong in Doctrine_Hydrator_Graph.

[DC-600] Query Cache causes exception when using array parameter and IN in a where clause

Wed, 21 Jul 2010 09:07:08 +0000

Following the documentation, I'm using an IN condition in a where clause on a Doctrine_Query with Query cache enabled (APC). Syntax:

$values = array(1, 2, 3, 4);

$q = Doctrine_Query::create()~~>from('SomeModel s')~~>where('s.column IN ?', array($values));

$results = $q->execute();

The first time this query is run, all is fine, and any subsequent runs will be fine as well, UNLESS the values array changes length, like so:

$values = array(1, 2, 3, 4, 5);

$q = Doctrine_Query::create()~~>from('SomeModel s')~~>where('s.column IN ?', array($values));

$results = $q->execute();

With the query cache enabled, this will throw a PDO "Invalid Parameter Count" exception, because it appears that Doctrine uses the cached query which only has 4 placeholders, but the passed parameters now has a count of 5.

A change in the length of the parameters array in this situation should cause Doctrine to insert a new entry into the query cache for this query.

Let me know if you need more information regarding this, if I find time I can try to put together a Test case.

Thanks!

[DC-601] When using a join and giving an alias to each select column the hyrdrator only returns one row.

Mon, 2 Aug 2010 02:45:07 +0000

Hi All
I am running into a strange problem using Doctrine-1.2.2-- I have a multi row result set but only the first row of it is returned in the hyrdated array that is generated.
I have tracked this down in the code to get a basic idea of whats going on – it seems that the $id variable in the hydrateResultSet function in Doctrine_Hydrator_Graph isn't being populated properly with data about the fields that are returning from my query. The _gatherRowData function seems to never detect that one of my columns is an identifier ("if ($cache[$key]['isIdentifier'])

{" doesn't return true ever so the next line of code: "$id[$dqlAlias] .= '|' . $value;" doesn't run). I think this is the problem but I don't totally understand how the mapping process is taking place in this function so can't be absolutely sure. This hydration problem goes away if I don't use left joins in my query, or if I use a query where not every field I am requesting is assigned an alias (at least one of the fields doesn't use the 'as' syntax). For instance this php: {code}

$q = Doctrine_Query::create();
$q->from('Customer Customer');
$q->leftJoin('Customer.Zip Zip');
$q->addSelect('Customer.firstname as first_name');
$q->addSelect('Customer.postalcode as postalcode');
$q->setHydrationMode(Doctrine::HYDRATE_ARRAY);

Generates this DQL:

SELECT Customer.firstname as first_name, Customer.postalcode as postalcode FROM Customer Customer LEFT JOIN Customer.Zip Zip

And this SQL:

SELECT c.firstname AS c_0, c.postalcode AS c_1 FROM customers c LEFT JOIN zips z ON c.postalcode = z.postalcode

Which results in this return after hyrdration:

array('0'=>array('first_name'=>'Armando', 'postalcode'=>'00659'))

However the following code hydrates just fine:

$q = Doctrine_Query::create();
$q->from('Customer Customer');
$q->addSelect('Customer.firstname as first_name');
$q->setHydrationMode(Doctrine::HYDRATE_ARRAY);

As does this code:

$q = Doctrine_Query::create();
$q->from('Customer Customer');
$q->leftJoin('Customer.Zip Zip');
$q->addSelect('Customer.firstname');
$q->addSelect('Customer.postalcode as postalcode');
$q->setHydrationMode(Doctrine::HYDRATE_ARRAY);

Here is the yaml for the sample data I am testing on:

detect_relations: false
package: Example
options:
type: INNODB
charset: utf8
Customer:
tableName: customers
columns:
customer_id:
type: integer(4)
primary: true
notnull: true
autoincrement: true
firstname:
type: string(45)
lastname:
type: string(45)
streetaddress:
type: string(45)
city:
type: string(45)
state:
type: string(45)
postalcode:
type: string(45)
relations:
Order:
type: many
local: customer_id
foreign: customer_id
Zip:
type: one
local: postalcode
foreign: postalcode
options:
type: InnoDB
Zip:
connection: default_schema
tableName: zips
columns:
postalcode:
type: varchar(30)
primary: true
latitude: 'float(10,6)'
longitude: 'float(10,6)'
city: string(50)
state: string(50)
country: string(50)
type: string(50)
relations:
Customer:
type: many
local: postalcode
foreign: postalcode

Perhaps there is something simple I am overlooking. To get around this I am just always selecting the primary key from my main table in every query.

Thanks in advance for any advice.
Will Ferrer

[DC-606] [Oracle] Query on M:M with relation name doesn't work

Mon, 29 Mar 2010 04:20:23 +0000

My schema:

---
Actuality:
  connection:         web
  tableName:          actuality
  actAs:
    softDelete:       ~
    Timestampable:    ~
    Sluggable:
      fields:         [name]
      builder:        [tool, slugify]
      indexName:      actuality_sluggable
      canUpdate:      true
  columns:
    id:
      type:           integer(4)
      primary:        true
      unsigned:       true
      sequence:       actuality
    created_at:
      type:           timestamp
    updated_at:
      type:           timestamp
    published_at:
      type:           timestamp
      notnull:        true
    unpublished_at:
      type:           timestamp
    name:
      type:           string(255)
      notnull:        true
    description_short:
      type:           string(1000)
      notnull:        true
    description:
      type:           clob
      notnull:        true
    is_professional:
      type:           boolean
      default:        true
  relations:
    Categories:
      class: ActualityCategory
      local: actuality_id
      foreign: actuality_category_id
      refClass: ActualityActualityCategory
      foreignAlias: Actualities

And my query:

public function retrieveCloud($is_professional, $limit = 20)
  {
    return $this->createQuery('ac')
    ->leftJoin('ac.Actualities a2')
    ->where('ac.id IN (SELECT aac.actuality_category_id FROM Actuality a LEFTJOIN a.ActualityActualityCategory aac WHERE a.published_at < ? AND a.is_professional = ?)', array(date('Y-m-d H:i:s'), $is_professional))
    ->orderBy('ac.name')
    ->limit($limit)
    ->execute();
  }

I have this error: Doctrine_Connection_Oracle_Exception

ORA-01008: not all variables bound : SELECT a.id AS a__id, a.created_at AS a__created_at, a.updated_at AS a__updated_at, a.name AS a__name, a.deleted_at AS a__deleted_at, a.slug AS a__slug, a2.id AS a2__id, a2.created_at AS a2__created_at, a2.updated_at AS a2__updated_at, a2.published_at AS a2__published_at, a2.unpublished_at AS a2__unpublished_at, a2.name AS a2__name, a2.description_short AS a2__description_short, a2.description AS a2__description, a2.is_professional AS a2__is_professional, a2.deleted_at AS a2__deleted_at, a2.slug AS a2__slug FROM actuality_category a LEFT JOIN actuality_actuality_category a3 ON (a.id = a3.actuality_category_id) LEFT JOIN actuality a2 ON a2.id = a3.actuality_id AND (a2.deleted_at IS NULL) WHERE a.id IN (SELECT a4.id FROM ( SELECT DISTINCT a4.id FROM actuality_category a4 LEFT JOIN actuality_actuality_category a6 ON (a4.id = a6.actuality_category_id) LEFT JOIN actuality a5 ON a5.id = a6.actuality_id AND (a5.deleted_at IS NULL) WHERE a4.id IN (SELECT a8.actuality_category_id AS a5__actuality_category_id FROM actuality a7 LEFT JOIN actuality_actuality_category a8 ON a7.id = a8.actuality_id WHERE (a7.published_at < :oci_b_var_1 AND a7.is_professional = :oci_b_var_2)) AND (a4.deleted_at IS NULL) ORDER BY a4.name ) a4 WHERE ROWNUM <= 20) AND (a.id IN (SELECT a5.actuality_category_id AS a5__actuality_category_id FROM actuality a4 LEFT JOIN actuality_actuality_category a5 ON a4.id = a5.actuality_id WHERE (a4.published_at < :oci_b_var_3 AND a4.is_professional = :oci_b_var_4)) AND (a.deleted_at IS NULL)) ORDER BY a.name

[DC-608] Limit and Offset breaks query with multiple non-join FROM statements

Tue, 30 Mar 2010 13:38:28 +0000

$query = $query->select('sf_guard_permission.id,
cms_section_translation.slug||\' \'||SUBSTRING("name", POSITION(\'@\' in "name") + 1) as name,
sf_guard_permission.description,
sf_guard_permission.created_at, sf_guard_permission.updated_at');
$query = $query->from('sfGuardPermission sf_guard_permission');
$query = $query->addfrom('CmsSection cms_section');
$query = $query->innerJoin('cms_section.WithCmsSectionTranslation cms_section_translation');
$query = $query->where('cast(SUBSTRING("name", 1, POSITION(\'@\' in "name") - 1) as integer) = cms_section.id');
$query = limit(20);
$query = offset(1);

Generated:

SELECT s.id AS s_id, s.description AS sdescription, s.created_at AS screated_at, s.updated_at AS supdated_at, c2.slug||' '||SUBSTR("name", POSITION('@' in "name") + 1) AS c2_0 FROM sf_guard_permission s, cms_section c INNER JOIN cms_section_translation c2 ON c.id = c2.sec_id WHERE s.id IN (SELECT doctrine_subquery_alias.id FROM (SELECT DISTINCT s2.id, c3.deleted_at FROM sf_guard_permission s2 cms_section c3 INNER JOIN cms_section_translation c4 ON c3.id = c4.sec_id WHERE cast(SUBSTR("name", 1, POSITION('@' in "name") - 1) as integer) = c3.id ORDER BY c3.deleted_at DESC LIMIT 20) AS doctrine_subquery_alias) AND (cast(SUBSTR("name", 1, POSITION('@' in "name") - 1) as integer) = c.id) ORDER BY c.deleted_at DESC

Notice:
SELECT DISTINCT s2.id, c3.deleted_at FROM sf_guard_permission s2 comma that is missing cms_section c3

[DC-609] Symfony doctrine doesnt save an M:M table if one of the tables is in a 1:1 relationship with another table

Wed, 31 Mar 2010 06:39:54 +0000

Symfony doctrine doesnt save an M:M table if one of the tables is in a 1:1 relationship with another table. Refer to Screen.png for ER diagram.

I have included the schema files as attachments.

You will notice in Screen shot 2010-03-31 at 3.30.56 AM.png, an item is selected in "Amenities list". When the form is submitted, everything saves in the db except for the item in the "Amenities list" (Screen shot 2010-03-31 at 3.31.37 AM.png)

[DC-610] Chaining innerjoins can only be made uni-directional; order matters

Fri, 31 Dec 2010 17:18:07 +0000

The following code fails

This doesn't work

Doctrine_Query::create()
	->select('Table t1')
	->innerJoin('f1.Foreign2 f2 WITH f1.field = 2')
	->innerJoin('t1.Foreign1 f1')

Doctrine seems only to be happy when we change the order of the inner joins

This works

Doctrine_Query::create()
	->select('Table t1')
	->innerJoin('t1.Foreign1 f1')
	->innerJoin('f1.Foreign2 f2 WITH f1.field = 2')

[DC-614] Separate the properties of the parent and the children

Fri, 2 Apr 2010 05:58:41 +0000

I want to talk about the inheritance, simple type and columns_aggregation.

Here an example of parent classes and two sub-classes : http://pastebin.com/5qJKtgp1
Here the generated models classes : http://pastebin.com/j2PmT7sd

To sum up : The parent class is Show, and the sub-classes are Video and Playlist.

A Show have a title.
A Video have a filename.
A Playlist have a user.

The problem that appear with the generated models, Is that the following code is working.
$playlist = Doctrine_Core::getTable ("Model_Playlist")->find (3);
$playlist->filename;

Or, the POO concept want that the filename property doesn't exist/available on a Playlist object. And Doctrine should throw an Exception ! Or, It is not the case.

The solution is to move the generated code of the sub-classes into there own classes.
Here the complete solution : http://pastebin.com/LzTG10P7

The problem with the one-to-one or many-to-many relationship is still the same.

The solution is more POO compliant.

[DC-615] New sequence generation for PostgreSQL SQL code results in errors

Sat, 22 Jan 2011 08:41:30 +0000

With 1.2.2 we get errors for our generated PostgreSQL code: "sequence <sequence name> already exists". I tracked down the issue to the following:

Doctrine_Export_Pgsql::createTableSql() has the following new code:

        if (isset($options['sequenceName'])) {
            $sql[] = $this->createSequenceSql($options['sequenceName']);
        }

This is fine, but this CREATE SEQUENCE code is now added after the CREATE TABLE code. This does not work okay for PostgreSQL, since PostgreSQL will automatically create the index for you if it does not yet exist. If CREATE SEQUENCE is required for some reason, then it should ge before the CREATE TABLE to be useful (it could for example be useful if different increment intervals or starting numbers should be set for the sequence).

I tried moving the new code up, but that did not yet give me the desired results. The issue is that Doctrine_Export::exportClassesSql() collects all the SQL in an array and finally does:

rsort($sql);
return $sql;

This can break any statement set in there that should be run in a specific order. For the PostgreSQL code, this will put all the CREATE TABLE calls in font of the CREATE SEQUENCE calls, resulting in the errors that we see.

Suggested fix options:

1) Do not sort the SQL queries, but accept them as generated by the db specific Export class (but I'm only suggesting this, because I am not aware of the reason to do an rsort() in the first place).

2) Change the PostgreSQL export code to make it immune to the sorting.

We did the latter in our code. The CREATE SEQUENCE and CREATE TABLE are concatenated into one statement string ("<squence>;<table>") that is added to the list of SQL queries. This provides us a work-around for the problem. The first solution is more clean IMO, but I lack knowledge to tell if the rsort() is here for technical or aesthetic reasons.

[DC-617] migration problem

Fri, 22 Jun 2012 14:01:48 +0000

I attached a testcase that reproduces all problem that I noticed (previously reported in "serious symfony doctrine:migrate issues - symfony 1.4" on symfony-dev)

There is a problem with an empty ON UPDATE when migrate to version 5

SQLSTATE[42601]: Syntax error: 7 BŁĄD: błąd składni w lub blisko "ON"
LINE 1: ... (object_c_id) REFERENCES object_c(id) ON UPDATE ON DELETE ...
^. Failing Query: "ALTER TABLE object_b ADD CONSTRAINT object_b_object_c_id_object_c_id FOREIGN KEY (object_c_id) REFERENCES object_c(id) ON UPDATE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE"

When migrateing from 5 to 3
Failing Query: "DROP INDEX object_b_object_c_id_idx" - this index doesn't exist - should be "object_b_object_c_id"

Also
$this->changeColumn('object_a', 'name', 'string', '2048', array(
));
$this->changeColumn('object_b', 'name', 'string', '2048', array(
));
doesn't work for me

[DC-618] [PATCH] Local key relations without modifed fields but with modified relations are not saved

Sun, 10 Jul 2011 23:28:08 +0000

Assume the following test setup:

[Email] * — 1 [Author] 1 — * [Book]

Assume further that you have a new Email, Author and Book object. Email and book have modified fields, author does not, except for the foreign key relation.

Now, when you save the Email object, the related Author is not saved because isModified($deep = false) returns false since no local field is modified. The solution is to pass the parameter $deep = true to isModified().

Patch and test case are attached. No existing test is broken by this fix.

PS: This patch fixes the correlated bug that objects with I18N behaviour are not saved if only their Translation objects are modified, but not their own fields.

[DC-619] preHydrate/postHydrate events do not use proper sub-class component

Mon, 14 Jun 2010 09:28:51 +0000

I am trying to use preHydrate/postHydrate with my models that use inheritance. The problem is that when using the parent table is used to query the records, the preHydrate/postHydrate events are passed to the parent record class instead of the proper sub-class for the current record.

Using the example schema below, if I do a findAll() on the Person table and it contained two Student records and one Professor record... preHydrate would get called on Person instead of Student and Professor. This also applies for any listeners that are registered on Student/Professor and not Person.

Person:
columns:
name:

{ type: string(50) }

Student:
inheritance:
extends: Person
type: column_aggregation
keyField: type
keyType: 1

Professor:
inheritance:
extends: Person
type: column_aggregation
keyField: type
keyValue: 2

[DC-623] Impossible to create non-unique slugs

Tue, 31 Aug 2010 11:51:12 +0000

I want to create a non-unique slug of a title field from my table.

But I've found that when I change unique from 'true' to 'false' the slugs were not created or updated

In lib\Doctrine\Template\Listener\Sluggable.php inside preUpdate() function the first if() statement disables the unique (false) option.

[DC-624] Validator_Readonly fails for new objects

Fri, 9 Apr 2010 13:52:37 +0000

If Readonly validator is on for some field, it fails when you trying to create new object (ie. by loading fixtures).

Fix proposition is in attachment.

[DC-625] Doctrine_Query throws exception for custom hydrator that extends stock hydrator

Tue, 20 Apr 2010 16:22:39 +0000

I have a custom hydrator that extends Doctrine_Hydrator_ScalarDriver, for the sole purpose of simplifying the column keys (by passing false as the 3rd parameter on _gatherRowData):

class Doctrine_Hydrator_AssocDriver extends Doctrine_Hydrator_ScalarDriver
{
public function hydrateResultSet($stmt)
{
$cache = array();
$result = array();

while ($data = $stmt->fetch(Doctrine_Core::FETCH_ASSOC))

{ $result[] = $this->_gatherRowData($data, $cache, false); }

return $result;
}
}

The processPendingFields method in Doctrine_Query is unnecessarily throwing a Doctrine_Query_Exception at line 465. This can be resolved by skipping hydration methods that extend None, Scalar and SingleScalar.

A diff of the changes is attached.

[DC-628] Two queries on the same table seems to share set of fields

Mon, 14 Jun 2010 09:24:49 +0000

Two queries:

1. $ab1 = Doctrine_Query::create()
->from('Model_UserAddressbook ab')
->leftJoin('ab.UserPersons up')
->leftJoin('ab.AdminUsers au'); // second one doesn't have this join

2. $ab2 = Doctrine_Query::create()
->from('Model_UserAddressbook ab')
->leftJoin('ab.UserPersons up');

When executing the following fetchOne:

A.) $x1 = $ab2->fetchOne()->toArray(); // has fields from addressbook, and subarray UserPersons, OK
B.) $x2 = $ab1->fetchOne()->toArray(); // has fields from addressbook, and subarray UserPersons and AdminUsers, OK
C.) $x3 = $ab2->fetchOne()->toArray(); // has fields from addressbook, and subarray UserPersons and AdminUsers, NOT OK

$x1 and $x3 should have the same set of fields, but $x3 has somehow received set of fields from $x2.

I haven't turned on any caching, but even if the caching is on, the result sets shouldn't mix, right?

I'm talking just about field names (set of fields), not fields data.

[DC-629] Doctrine Integer Validator should use intval() rather than round(floatval())

Tue, 8 Jun 2010 17:13:14 +0000

echo PHP_INT_MAX;
echo "\n";
echo strval(round(floatval(PHP_INT_MAX)));

on 64 bit machine, default php install, you get:

9223372036854775807
9.22337203685E+18

float precision is set to 12 by default. setting it higher offers no benefit, with it set to 20+, it still doesn't match up (and is actually not reliably past a certain length, i'd have to dig again to find a reference though), but as you can see, no go:

9223372036854775807
9223372036854775808

as a result, very large #'s do NOT validate as doctrine integers, even though they are.

fix, use intval() instead. as far as I can tell, and as far as our 400+ unit tests in our application show, PHP_INT_MAX is fully supported everywhere else except for in Validator.php@170:

170c170
<                  return (string) $var == strval(round(floatval($var)));
---
>                  return (string) $var == strval(intval($var));

[DC-630] Add Undelete functionality to SoftDelete behaviour

Thu, 15 Apr 2010 01:35:57 +0000

Can an undelete function be added to the Doctrine ORM which will reset deleted_at fields to null and conform to cascade rules (just as the original delete did)?

[DC-631] Documentation

Thu, 15 Apr 2010 05:18:30 +0000

http://www.doctrine-project.org/Doctrine_Record/1_2#method_importfrom

The description of the $type parameter is : Format type: xml, yml, json
But it could take an array.

So the documentation have to be update for this point.

[DC-634] getPopularTags() query fails on Postgresql

Thu, 15 Apr 2010 14:47:56 +0000

When I run:
Doctrine::getTable('TaggableTag')->getPopularTags();
I get: ERROR: column "i2__1" does not exist

The failing query on PostgreSql is:

SELECT t.id AS t_id, t.name AS tname, COUNT(DISTINCT i.id) AS i_0,
(COUNT(DISTINCT i.id)) AS i__1
FROM taggable_tag t
LEFT JOIN cms_model_image_taggable_tag c ON (t.id = c.tag_id)
LEFT JOIN image i ON i.id = c.id
WHERE t.id IN
(SELECT doctrine_subquery_alias.id
FROM
(SELECT DISTINCT t2.id, (COUNT(DISTINCT i2.id)) AS i2__1
FROM taggable_tag t2
LEFT JOIN cms_model_image_taggable_tag c2 ON (t2.id = c2.tag_id)
LEFT JOIN image i2 ON i2.id = c2.id
GROUP BY t2.id HAVING i2__1 > 0
ORDER BY i2__1 DESC LIMIT 10) AS doctrine_subquery_alias)
GROUP BY t.id HAVING i__1 > 0
ORDER BY i__1 DESC

Seems that this just a PostgreSql issue.
On Mysql it runs just fine.

The corrected, working query is:

SELECT t.id AS t_id, t.name AS tname, COUNT(DISTINCT i.id) AS i_0,
(COUNT(DISTINCT i.id)) AS i__1
FROM taggable_tag t
LEFT JOIN cms_model_image_taggable_tag c ON (t.id = c.tag_id)
LEFT JOIN image i ON i.id = c.id
WHERE t.id IN
(SELECT doctrine_subquery_alias.id
FROM
(SELECT DISTINCT t2.id, (COUNT(DISTINCT i2.id)) AS i2__1
FROM taggable_tag t2
LEFT JOIN cms_model_image_taggable_tag c2 ON (t2.id = c2.tag_id)
LEFT JOIN image i2 ON i2.id = c2.id
GROUP BY t2.id HAVING COUNT(DISTINCT i2.id) > 0
ORDER BY i2__1 DESC LIMIT 10) AS doctrine_subquery_alias)
GROUP BY t.id, t.name HAVING COUNT(DISTINCT i.id) > 0
ORDER BY i__1 DESC

For more details, please read the discussion here:
http://stackoverflow.com/questions/2647537/doctrine-sql-query-works-on-mysql-on-postgresql-wont

[DC-635] synchronizeWithArray and link-table

Fri, 16 Apr 2010 09:07:30 +0000

Tree tables : tags, compo_show_tag, shows

"compo_show_tag" make a link between tags and shows. It's a many-to-many relationship.

Assume that all the Tags / Shows are already create. The max id is 300 for shows and tags.

$itemArray = array ();
$itemArray["_identifier"] = 38;
$itemArray["shows"][0]["_identifier"] = 36;
$itemArray["shows"][1]["_identifier"] = 200;

$item = new Model_Tag ();
$item->synchronizeWithArray($itemArray, true);

echo $item->shows[0]->idShow; //Output : 36
echo $item->shows[1]->idShow; //Output : 200

$item->save ();

Above create two entry into the compo_show_table. Because all element are existing.

$itemArray = array ();
$itemArray["_identifier"] = 38;
$itemArray["shows"][0]["_identifier"] = 36;

$item = new Model_Tag ();
$item->synchronizeWithArray($itemArray, true);

echo $item->shows[0]->idShow; //Output : 36

$item->save ();

Above remove the relation between Show#200 and Tag#38, but keep the relation between Show#36 and Tag#38.

$itemArray = array ();
$itemArray["_identifier"] = 38;
$itemArray["shows"][0]["_identifier"] = 36;
$itemArray["shows"][1]["_identifier"] = 150;
$item = new Model_Tag ();
$item->synchronizeWithArray($itemArray, true);

echo $item->shows[0]->idShow; //Output : 36
echo $item->shows[1]->idShow; //Output : 150

$item->save ();

Above create a new relation, like the first example.

$itemArray = array ();
$itemArray["_identifier"] = 38;
$itemArray["shows"][0]["_identifier"] = 36;
$itemArray["shows"][1]["_identifier"] = 140;

$item = new Model_Tag ();
$item->synchronizeWithArray($itemArray, true);

echo $item->shows[0]->idShow; //Output : 36
echo $item->shows[1]->idShow; //Output : 140

$item->save ();

Bug is above.
We except that Doctrine remove the relation between Show#150 and Tag#38 and add a new one between Show#140 and Tag#38.
Here the bug because Doctrine doesn't change anything.

Thanks.
Armetiz.

[DC-637] Many-to-many: Using Association Class (refclass) property in query adds leftJoin

Tue, 20 Apr 2010 06:39:21 +0000

When trying to use a refclass property - i.e. normalization table column - in a query, an unnecessary join is added to the query created, which is then used to "access" the property.

This issue has already been discussed back in May 2008 but still seems to persist.
Please see the google group discussion http://groups.google.com/group/doctrine-user/browse_thread/thread/c655832a450ccd1a/9cb6eca6ae1c3dee for example + comments.

Unfortunately it is hardly possible to write a test case for this, as working SQL is generated, but the query is just not right (test case basically would have to assert the query string, wich does not make much sense).
Another way to test if it does "what it should", could be to assert contents of $q->getTableAliasMap() - but does not seem ideal either.

John Wage commented on this issue
"Can you create a ticket for this with a failing test case? I believe this
should be possible and we should investigate a fix for it.
Thanks, Jon "
http://groups.google.com/group/doctrine-user/browse_thread/thread/c655832a450ccd1a/9cb6eca6ae1c3dee#msg_c73934a38515cadb

[DC-640] Slugs aren't created when inserting/updating a table row

Mon, 3 May 2010 08:31:15 +0000

Basically the slug column doesn't get updated in spite of all fields being added correctly, as far as i can tell.
It seems to be related to additional options because when i don't have either of the uniqueBy or canUpdate options specified, it just works.

What's been missing is the 'slug' column value in the sql statements (providing 3 examples):

2400 Query INSERT INTO `custom_category` (`block_id`, `name`) VALUES ('1', 'slug test')
2526 Query INSERT INTO `custom_category` (`name`, `block_id`) VALUES ('please do work..', '1')
2560 Query UPDATE `custom_category` SET `name` = 'still not ok' WHERE `id` = '12'

The generated schema.sql includes the correct create table statement (it's also correctly inserted in the db):

CREATE TABLE `custom_category` (
  `id` INT UNSIGNED AUTO_INCREMENT,
  `name` VARCHAR(255) NOT NULL,
  `block_id` INT UNSIGNED NOT NULL,
  `slug` VARCHAR(255),
  UNIQUE INDEX `custom_category_sluggable_idx` (`slug`, `block_id`, `name`),
  INDEX `block_id_idx` (`block_id`),
  PRIMARY KEY(`id`)
) ENGINE = INNODB;

The schema.yml entry is the following:

CustomCategory:
  connection: removed
  tableName: custom_category
  actAs:
    Sluggable:
      fields: [name]
      uniqueBy: [block_id, name]
      canUpdate: true
  columns:
    id:
      type: integer(4)
      unsigned: true
      notnull: true
      primary: true
      autoincrement: true
    name:
      type: string(255)
      notnull: true
    block_id:
      type: integer(4)
      unsigned: true
      notnull: true
  relations:
    Products:
      class: Product
      foreignAlias: CustomCategories
      refClass: ProductCustomCategory
    Block:
      class: Block
      local: block_id
      foreign: id
      foreignType: many
      foreignAlias: CustomCategories
      type: one

And finally the appropriate auto generated base class (removed doc block):

<?php
// Connection Component Binding
Doctrine_Manager::getInstance()->bindComponent('CustomCategory', 'removed');

abstract class BaseCustomCategory extends aaDoctrineRecord
{
    public function setTableDefinition()
    {
        $this->setTableName('custom_category');
        $this->hasColumn('id', 'integer', 4, array(
             'type' => 'integer',
             'unsigned' => true,
             'primary' => true,
             'autoincrement' => true,
             'length' => '4',
             ));
        $this->hasColumn('name', 'string', 255, array(
             'type' => 'string',
             'notnull' => true,
             'length' => '255',
             ));
        $this->hasColumn('block_id', 'integer', 4, array(
             'type' => 'integer',
             'unsigned' => true,
             'notnull' => true,
             'length' => '4',
             ));
    }

    public function setUp()
    {
        parent::setUp();
        $this->hasMany('Product as Products', array(
             'refClass' => 'ProductCustomCategory',
             'local' => 'custom_category_id',
             'foreign' => 'product_id'));

        $this->hasOne('Block', array(
             'local' => 'block_id',
             'foreign' => 'id'));

        $sluggable0 = new Doctrine_Template_Sluggable(array(
             'fields' =>
             array(
              0 => 'name',
             ),
             'uniqueBy' =>
             array(
              0 => 'block_id',
              1 => 'name',
             ),
             'canUpdate' => true,
             ));
        $this->actAs($sluggable0);
    }
}

[DC-643] Doctrine_Collection problem duplicate record

Thu, 22 Apr 2010 09:53:22 +0000

$oVideo = Doctrine_Core::getTable ("Model_Video")->find (500);
$oVideo = new Model_Video ();
$oVideo->assignIdentifier (500);

$oTag = Doctrine_Core::getTable ("Model_Tag")->find (500);
$oVideo->tags->clear ();
$oVideo->tags[] = $oTag;
$oVideo->save ();

The previous code can be execute a lot of time.

Now, let us create the Doctrine_Collection.

$oVideo = Doctrine_Core::getTable ("Model_Video")->find (500);
$oVideo = new Model_Video ();
$oVideo->assignIdentifier (500);

$oTag = Doctrine_Core::getTable ("Model_Tag")->find (500);
$oVideo->tags = new Doctrine_Collection ("Model_Tag");
$oVideo->tags[] = $oTag;
$oVideo->save ();

Doctrine create a relation between the video and tag. It doesn't update it.
If the relation already exists into the database, Doctrine create an other record, or the DB throw an integrity error if you have constraint.

[DC-648] Behavior geographical generates latitude DOUBLE(18, 2), longitude DOUBLE(18, 2) - it's not exact

Wed, 19 Jan 2011 05:26:19 +0000

The problem was already described by another person at http://www.doctrine-project.org/jira/browse/DC-385
and was fixed but now is broken again.

When using the Geographical behaviour in a YML schema the latitude is stored in Mysql as a Double(18,2) instead of a Double as it was in the previous versions. It appears that all doubles in yml are defaulting to (18,2).

[DC-649] Getting Doctrine_Validator_Exception on Doctrine_Record::replace() when using unique

Mon, 26 Apr 2010 11:41:15 +0000

Using this code:

$user = new User();
$user->mail = 'mail@mail.mail';
$user->save();
$user2 = new User();
$user2->mail = 'mail@mail.mail';
$user2->replace();

I get the following exception:

Fatal error: Uncaught exception 'Doctrine_Validator_Exception' with message 'Validation failed in class User: 1 field had validation error: 1 validator failed on mail (unique)' in D:\Workspace\Doctrine\Doctrine\Transaction.php:265
Stack trace:
#0 D:\Workspace\Doctrine\Doctrine\Connection.php(1395): Doctrine_Transaction->commit(NULL)
#1 D:\Workspace\Doctrine\Doctrine\Connection\UnitOfWork.php(143): Doctrine_Connection->commit()
#2 D:\Workspace\Doctrine\Doctrine\Record.php(1748): Doctrine_Connection_UnitOfWork->saveGraph(Object(User), true)
#3 D:\Workspace\test.php: Doctrine_Record->replace()
#4

{main}

thrown in D:\Workspace\Doctrine\Doctrine\Transaction.php on line 265

[DC-651] [PATCH] Doctrine_Record::option('orderBy', ...) of join's right side being applied to refTable in m2m relationship

Wed, 31 Aug 2011 12:43:09 +0000

When using the Doctrine_Record::option('orderBy', ...) feature on a table definition, where that table is the target of a many-to-many join, the specified orderBy columns are applied to the relation table's alias. So for example, given the following definitions:

class User extends Doctrine_Record {
  public function setTableDefinition() {
    $this->hasColumn('uid', 'integer', null, array('primary' => true));
    $this->option('orderBy', 'uid');
  }

  public function setUp() {
    $this->hasMany('Group as groups', array('refClass' => 'UserGroup', 'local' => 'user_uid', 'foreign' => 'group_id'));
  }
}

class Group extends Doctrine_Record {
  public function setTableDefinition() {
    $this->hasColumn('gid', 'integer', null, array('primary' => true));
  }

  public function setUp() {
    $this->hasMany('User as users', array('refClass' => 'UserGroup', 'local' => 'group_gid', 'foreign' => 'user_id'));
  }
}

class UserGroup extends Doctrine_Record {
  public function setTableDefinition() {
    $this->hasColumn('user_uid', 'integer', null, array('primary' => true));
    $this->hasColumn('group_gid', 'integer', null, array('primary' => true));
  }

  public function setUp() {
    $this->hasOne('User as user', array('local' => 'user_uid', 'foreign' => 'uid'));
    $this->hasOne('Group as group', array('local' => 'group_gid', 'foreign' => 'gid'));
  }
}

the following queries:

$query = Doctrine_Query::create()
  ->select('u.*')
  ->from('User u')
  ->leftJoin('u.groups g WITH g.gid=?', 1);
echo $query->getSqlQuery() . "\n";

$query = Doctrine_Query::create()
  ->select('g.*')
  ->from('Group g')
  ->leftJoin('g.users u WITH u.uid=?', 1);
echo $query->getSqlQuery() . "\n";

will output the following:

SELECT u.uid AS u__uid FROM user u LEFT JOIN user_group u2 ON (u.uid = u2.user_uid) LEFT JOIN group g ON g.gid = u2.group_id AND (g.gid = ?) ORDER BY u.uid
SELECT g.gid AS g__gid FROM group g LEFT JOIN user_group u2 ON (g.gid = u2.group_gid) LEFT JOIN user u ON u.uid = u2.user_id AND (u.uid = ?) ORDER BY u.uid, u2.uid

The orderBy option() call is applied to the User definition. The SQL for the first query is correct (where User is on the left side of the join). The SQL for the second query (where User is on the right-most side of the join), however, is obviously incorrect (UserGroup doesn't even have a uid column). Basically, User's orderBy option is being applied to both the User table and its respective reference table, UserGroup, when it is the target of a join.

After digging through the source for a while, I believe I've come up with a patch for this issue (which should be checked by someone more knowledgeable of Doctrine's internals). Basically, in the Doctrine_Query::buildSqlQuery() function, a call is made to Doctrine_Relation::getOrderByStatement() with the reference table (UserGroup)'s alias (u2), which in turn makes a call to Doctrine_Table::getOrderByStatement() on the referenced table (User), filling in the ORDER BY clause with User columns using UserGroup's alias. My solution was to reorder the logic so that the test for a reference class is made before the initial call to getOrderByStatement() is made. It seems to work against my test case and the test cases in the repository. I'll post my patch momentarily.

This bug was first mentioned in the comments in DC-313, but the original ticket comes across as more of a feature request for the hasMany() orderBy feature.

[DC-652] unidirectionnal hasMany definition

Mon, 14 Jun 2010 09:29:07 +0000

Here the definition of the Domain Model : http://pastebin.com/i80d73s8

To resume, Show is a mother class. Video, is a direct extend from Show.
ShowContainer is an abstract class that expend Show. It define an hasMany relation to Video, through CompoShowShow.
Program and Playlist are extends ShowContainer.

the following DQL Query work fine.

$query = Doctrine_Query::create ()
->from ("Model_Program program")
->leftJoin ("program.children children");
$oShow = $query->fetchOne ();
var_dump (get_class ($oShow->children[0])); //Output Model_Video

But, the following code isn't working :

$oProgram = Doctrine_Core::getTable ("Model_Program")->find (2);
$oProgram->children;

//Throw Exception
//Message: Unknown record property / related component "children" on "Model_Program"
//Doctrine\Record.php(1381)

The Program#2 is in the database.

Here we are.

[DC-655] When Export from Models to database is made some constraints may not be created

Fri, 11 Jun 2010 09:05:00 +0000

When exporting my schema from yaml I noticed that some CONSTRAINT are not created, but all the models are. After analyzing the code I found that an issue is not related to YAML but is related to Doctrine_Table::getExportableFormat(). I have models creation option to create it in PEAR-like style.

So, when you have a schema like this:

----------------
Partner_Code:
tableName: partner_code
columns:
id:
type: integer(4)
unsigned: true
primary: true
autoincrement: true
notnull: true
code:
type: string(64)
unique: true
notnull: true

Partner_Channel:
tableName: partner_channel
columns:
id:
type: integer(4)
unsigned: true
primary: true
autoincrement: true
notnull: true
name:
type: string(64)
notnull: true
relations:
Codes:
class: Partner_Code
local: channel_id
foreign: code_id
refClass: Partner_Channel_Code
foreignAlias: Partner_Channel
foreignType: one
type: many

Partner_Channel_Code:
tableName: partner_channel_x_code
columns:
channel_id:
type: integer(4)
unsigned: true
primary: true
notnull: true
code_id:
type: integer(4)
unsigned: true
primary: true
notnull: true
----------------

it generates sql like this:

----------------
CREATE TABLE partner_channel (id INT UNSIGNED AUTO_INCREMENT, name VARCHAR(64) NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
CREATE TABLE partner_channel_x_code (channel_id INT UNSIGNED, code_id INT UNSIGNED, PRIMARY KEY(channel_id, code_id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
CREATE TABLE partner_code (id INT UNSIGNED AUTO_INCREMENT, code VARCHAR(64) NOT NULL UNIQUE, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
ALTER TABLE partner_channel_x_code ADD CONSTRAINT partner_channel_x_code_channel_id_partner_channel_id FOREIGN KEY (channel_id) REFERENCES partner_channel(id);
----------------

But should also generate:

----------------
ALTER TABLE partner_channel_x_code ADD CONSTRAINT partner_channel_x_code_code_id_partner_code_id FOREIGN KEY (code_id) REFERENCES partner_code(id);
----------------

But if I just change the schema with this changes (notice the Channel changed to Shannel):

----------------
Partner_Channel:
relations:
Codes:
refClass: Partner_Shannel_Code

Partner_Shannel_Code:
tableName: partner_channel_x_code
----------------

Everything is created.

----------------
CREATE TABLE partner_channel (id INT UNSIGNED AUTO_INCREMENT, name VARCHAR(64) NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
CREATE TABLE partner_code (id INT UNSIGNED AUTO_INCREMENT, code VARCHAR(64) NOT NULL UNIQUE, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
CREATE TABLE partner_channel_x_code (channel_id INT UNSIGNED, code_id INT UNSIGNED, PRIMARY KEY(channel_id, code_id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci ENGINE = INNODB;
ALTER TABLE partner_channel_x_code ADD CONSTRAINT partner_channel_x_code_code_id_partner_code_id FOREIGN KEY (code_id) REFERENCES partner_code(id);
ALTER TABLE partner_channel_x_code ADD CONSTRAINT partner_channel_x_code_channel_id_partner_channel_id FOREIGN KEY (channel_id) REFERENCES partner_channel(id);
----------------

So as I figured out is that when creating the tables alphabetic order has an influence on creating the CONSTRAINT for that Model in sql. I suppose line 715 of the Doctrine/Table.php near $key = $this->_checkForeignKeyExists(...) is operating, but I am not sure (when inserting into DB some tables are not created yet?).

Do not know how to markup here, it's my first issue in Jira, please press "edit" to see the yaml code formatted

[DC-661] Subquery Doctrine Couldn't find class

Tue, 8 Jun 2010 14:09:05 +0000

I'm trying to create a query like this one :

SELECT nombre, (select count( * ) from alojamiento a left join localidad l on a.localidad_id=l.id where p.id=l.provincia_id and a.activo=true) as total from provincia p

$q = Doctrine_Query::create()
->select('p.nombre')
->addSelect('(select count( * ) from alojamiento a left join
localidad l on a.localidad_id=l.id where p.id=l.provincia_id and
a.activo=true)')
->from('provincia p');

but it fails : error 500, couldn't find class a.

And :
$q = Doctrine_Query::create() ->select('nombre') ->addSelect('(select count( * ) from alojamiento left join localidad on
alojamiento.localidad_id=localidad.id where
provincia.id=localidad.provincia_id and alojamiento.activo=true)') ->from('provincia');

leads to : SQLSTATE[42S22]: Column not found: 1054 Unknown column 'a.localidad_id' in 'on clause'.

[DC-666] Unable to create relations with several fields

Sat, 7 Aug 2010 15:38:53 +0000

I have 2 tables.

t1 :

id [Primary Key]
field1
field2
...
fieldn
t2_id [related to t2.id]
—
primary key: id

t2:
—
id [related to t1.t2_id]
fixed_set [predefined set of values (for example "a", "b", "c")]
field1
field2
...
fieldn
—
primary key: id + fixed_set

I need to use relation like follows:
SELECT *
FROM t1
LEFT JOIN t2 ON (t1.t2_id = t2.id AND t2.fixed_set = "a")

There is followed text in phpdoc from Relation.php:
—

local the local field(s)
*
foreign the foreign reference field(s)
—

But it is unable to use several fields in "local" and "foreign", only one "local" and "foreign" field.

[DC-667] migration fails for long foreign key names

Thu, 6 May 2010 09:19:20 +0000

When having a model with short name and i18n field which is versioned, everthing is right. There are no problems when doing diff and migration again and again. Nothing will happen because nothing changed.
For example:
mytest:
actAs:
I18n:
fields: [ description_front ]
actAs:
Timestampable:
Versionable:
columns:
title:

{type: string(255)}

description_front:

{type: string(255)}

But when using a longer model name like 'mytestmytestmytest' then some strange errors occurred in my simple example. After creating the 'translation' and 'transalation_version' table in '1273139712_version2.php' and creating the foreign keys in '1273139713_version3.php' there shouldn'd be a '1273146011_version4.php' generated by doing a diff, because everthing was already done. And of course when doing a migration with this last version, you will get errors.

[DC-668] Call to undefined method Doctrine_Adapter_Mysqli::setAttribute()

Tue, 8 Jun 2010 11:57:44 +0000

i'm trying to switch to php5.3.1.
using the same connection as before, mysql://, i get

Warning: PDO::__construct() [pdo.--construct]: OK packet 6 bytes shorter than expected in C:\wamp\bin\php\php5.2.9-2\PEAR\Doctrine\lib\Doctrine\Connection.php on line 470

after researching this error, i found out that it is related to the new password in mysql5.
i tried changing the password for the connection, and made sure there is no old_password set in my.ini, without any success.

so i'm trying to connect using mysqli adapter, and now i get this error:
PHP Fatal error: Call to undefined method Doctrine_Adapter_Mysqli::setAttribute() in C:\wamp\bin\php\php5.2.9-2\PEAR\Doctrine\lib\Doctrine\Connection.php on line 496

how can i connect to mysql5.1 with php5.3, and what is the best connection to pick. mysql or mysqli.

[DC-676] Validation exception thrown only if internal nesting level == 1

Tue, 8 Jun 2010 16:20:02 +0000

I wonder why Validation exception is thrown only if internal nesting level of transaction is 1 and the manual nesting level is not considered.

Line 262 - lib/Doctrine/Transaction.php:

if ($this->_internalNestingLevel == 1) {
    $tmp = $this->invalid;
    $this->invalid = array();
    throw new Doctrine_Validator_Exception($tmp);
}

I have a large database with a lot of tables and relationships. At some case the validation exception is not thrown if the validation fails.

If I add $this->_nestingLevel into this condition:

if ($this->_internalNestingLevel == 1 || $this->_nestingLevel == 1) {
    $tmp = $this->invalid;
    $this->invalid = array();
    throw new Doctrine_Validator_Exception($tmp);
}

Then the validation exception is thrown as excepted.

I don't know why you ignore here the nesting level.

It would be great if you could explain me more about these lines.

I ran the unit test with this modification and got the same result.

[DC-680] HYDRATE_ARRAY causes timeout with no fields selected

Thu, 13 May 2010 14:42:20 +0000

Calling HYDRATE_ARRAY on a query with

a) No values selected
b) select('*')
c) select('Table.*')

causes the entire query object to be loaded, rather than just returning an array of all values. If a limit(1) is used, the correct result is returned. But as soon as it becomes a collection, the entire query object is returned.

Code to produce problem..

$query = Doctrine_Query::create()
        ->from('Order ord')
        ->limit(2)
        ->execute(array(), Doctrine_Core::HYDRATE_ARRAY);
        
        print_r($query);

[DC-684] After adding a Reference, the ForeignKeys in the DB are not updatet

Tue, 26 Oct 2010 08:13:33 +0000

After query a record from the DB, where a foreign key is null, and changing only the reference belonging to this foreign key, and only these reference no other value of the record, a save of the record doesn't lead to a change in the foreign key field.

For example: I'll save a user record with some data of a regestration and give him the possibillity to add a city where he cames from later in his account settings, if no other user attribute is changed, the state of the user record is still CLEAN. The result is that I can access the user->City property correctly only as long as no refresh from the db is done. So the changing of the foreign key belonging to the city isn't persistent in the DB.

Example Code:
$user = new Model_User();
$user->firstName = md5(rand());
$user->save();

$id = $user->id;
unset($user);
assert(! $user);

$user = Model_UserTable::getInstance()->find($id);
assert(!$user->relatedExists('City'));

$user->City->name = 'Mainz';
$user->save();
unset($user);

$user = Model_UserTable::getInstance()->find($id);
$user->refresh(true);
assert($user->City->name == 'Mainz');

The last assert failse. I realized the problem while updating just a referenz using the fromArray() method like $user->City->fromArray(). The city would be saved correctly in DB but the foreign key in the user table would not be updated. After debugging I recognized that the $user is not replaced in UnitOfWork::saveGraph() because the $user is still in CLEAN state.

Using " $user->coreSetRelated('Country', $user->Country);" or "$user->state(Doctrine_Record::STATE_DIRTY);" after "$user->City->name = 'Mainz'" would fix the prob in this case. As well as creating a new City instance an set $user->City with this instance like:

$city = new Model_City();
$city->name = 'Mainz';
$user->City = $city;

Also $user->isModified(true) is true. So I fixed the issues in my case by changing the state of my records to DIRTY if the "$this->state() == CLEAN && $user->isModified(true) == true" in the preSave() method of an abstract class that my Base classes are extending....

[DC-689] Columns of type 'array' adds default clause to the create table statement which isn't supported by MySQL.

Fri, 11 Jun 2010 08:31:26 +0000

The column type 'array' creates a column of the type 'LONGTEXT' but also adds the default value to the column declaration which makes the creation of the table fail.

MySQL does not support default values for TEXT, BLOB or LONGTEXT. I don't know when this behavior was added to MySQL or if it always has been like that. MySQL 5.0.51 will accept it without any SQL mode set, 5.0.83 won't.

[DC-692] Can not create a subquery in where

Wed, 19 May 2010 00:18:41 +0000

Hi All

I can not figure out how to make a subquery work in doctrine. I get the subquery to look fine in DQL but when doctrine converts the DQL to SQL the subquery is automatically removed.

Here is an example:
This PHP:

$q = Doctrine_Query::create(); 
$q->from('Customer Customer'); 
$q->addWhere(' Customer.id in (SELECT Customer.id as customer_id FROM Customer Customer)'); 
$q->addSelect('Customer.id'); 
$q->addSelect('Customer.id as customer_id');
$q->limit(20);

Creates this DQL:

SELECT Customer.id, Customer.id as customer_id FROM Customer Customer WHERE Customer.id in (SELECT Customer.id as customer_id FROM Customer Customer) LIMIT 20

Which creates this broken SQL:

SELECT p.id AS p__id, p.id AS p__0 FROM product_customers p WHERE (p.id in ()) LIMIT 20

Notice that the subquery has been replaced with just "()".

Is there something wrong with my execution, does doctrine just not support subqueries, or is there a bug here?

Thanks much in advance.

Sincerely

Will Ferrer

[DC-704] Where fields not escaped properly when deleting associations.

Mon, 14 Jun 2010 08:26:40 +0000

We noticed that in both Doctrine/Record.php and Doctrine/Connection/UnitOfWork.php the fields in the where clause arent being escaped properly. A few of our fields happen to be keywords, but it seems that these queries arent escaping the names of fields that happen to be keywords.

I have verified the field name is in the keywords list for my driver.

This happens near the following code:
Doctrine/Record.php:2465
Doctrine/Record.php:2476
Doctrine/Connection/UnitOfWork.php: 443

[DC-707] When inserting node as direct children of a root node, it seems the root node is not populated with new lft/rgt values...

Sat, 7 Aug 2010 15:39:17 +0000

Hi,

When inserting node as direct children of a root node, it seems the root node is not populated with new lft/rgt values...

Here is a test case, simply made of the code samples given in documentation :
http://www.doctrine-project.org/projects/orm/1.2/docs/manual/hierarchical-data/en#nested-set:working-with-trees:creating-a-root-node

/*
 * Creating a Root Node
 */
$category = new Category();
$category->name = 'Root Category 1';
$category->save();

$treeObject = Doctrine_Core::getTable('Category')->getTree();
$treeObject->createRoot($category);


/*
 * Inserting a Node
 */
$child1 = new Category();
$child1->name = 'Child Category 1';

$child2 = new Category();
$child2->name = 'Child Category 1';

$child1->getNode()->insertAsLastChildOf($category);
$child2->getNode()->insertAsLastChildOf($category);




/*
 * BUGGY !
 */
$category->getNode()->hasChildren();   // will return false, we except true as we just instert 2 children to this root node...


$category->refresh();
$category->getNode()->hasChildren(); // true... that's now ok !

[DC-708] Wrong definition for MySQL string primary column

Mon, 12 Jul 2010 16:32:44 +0000

If you define a primary column, the attribute notnull is removed from the column definition because Doctrine assumes that primary columns are always not null.

Now suppose you have a schema like this, with a string primary column.

Client:
  columns:
    serial:    { type: string(50), notnull: true, primary: true }
    name:      { type: string(36), notnull: true }

That's fine, but causes problems with MySQL where the column is created with a default value of "" (empty string) and not <none>.

CREATE TABLE client (serial VARCHAR(50), name VARCHAR(36) NOT NULL, PRIMARY KEY(serial)) ENGINE = INNODB;

Note that the 2nd column is well defined and has <none> as default value (as seen from phpMyAdmin).

I attached a quick-workaround to disable the code which removes the notnull attribute from column definition.

After that the SQL code is like this:

CREATE TABLE client (serial VARCHAR(50) NOT NULL, name VARCHAR(36) NOT NULL, PRIMARY KEY(serial)) ENGINE = INNODB;

[DC-722] String(512) is being implemented as TEXT instead varchar(512) on MySQL

Tue, 8 Jun 2010 23:49:39 +0000

Well
the titles says it all.

Just now I realized the TEXT type for fields that I've defined in the code as String(512).
What I understand is that TEXT has performance disvantages. Why not use varchar when there are little needs instead TEXT?

Thanks in advice.
Greetings!

[DC-723] String = 512 becomes TEXT

Wed, 9 Jun 2010 13:04:27 +0000

I don't know if this is a feature or a bug, but if I define a field type = string, length = 512, Doctrine creates this as a TEXT field in MySQL. Seems to do this for a length over 255 characters, e.g. 256. This seems like overkill possibly. Feels like the field should be defined either as TINYTEXT or VARCHAR (which can go up to 63335 characters in length).

Is there any way to control this behavior?

[DC-724] Blameable relations import problem

Tue, 13 Jul 2010 07:00:31 +0000

The import works only when i DISABLE the update relation. When i activate the update relation i get an sql error

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`clubicious`.`location`, CONSTRAINT `location_updated_by_sf_guard_user_id` FOREIGN KEY (`updated_by`) REFERENCES `sf_guard_user` (`id`))

The relation is created correct i think the problem is in the importer???

Location:
actAs:
Timestampable: ~
Sortable: ~
Blameable:
columns:
created:
length: null
updated:
length: null
relations:
created:
disabled: false
class: sfGuardUser
updated:
disabled: false
class: sfGuardUser
columns:
name:

{ type: string(255), notnull: true }

My fixtures:
sfGuardUser:
gfranke:
id: 1
first_name: Gordon
last_name: Franke
email_address: franke@clubicious.com
username: gfranke
password: startgf
Location:
location_atomic:
name: Atomic Cafe
CreatedBy: gfranke
UpdatedBy: gfranke

location_max:
name: Max & Moritz
CreatedBy: gfranke
UpdatedBy: gfranke

[DC-727] ReOpen DC-46 - Unexpected behavior with whereIn() and empty array

Wed, 12 Oct 2011 10:45:42 +0000

I reopen the ~~DC-46~~ as it'seems not fix at all.
When I do a whereIn with empty array, the condition is just drop and I get no Exception.

Here is a simple test case:

require_once('doctrine/lib/Doctrine.php');
spl_autoload_register(array('Doctrine', 'autoload'));
$manager = Doctrine_Manager::getInstance();
$manager->setAttribute(Doctrine::ATTR_EXPORT, Doctrine::EXPORT_ALL);
$conn = Doctrine_Manager::connection('mysql://root:root@localhost/test_doctrine');
echo "Connection is set up\n";

class Record extends Doctrine_Record {
    public function setTableDefinition(){
        $this->setTableName('record');
    }
}

// Create the db
try {Doctrine::dropDatabases();}catch(Exception $e){} // Drop if exist :-)
Doctrine::createDatabases();Doctrine::createTablesFromArray(array('Record'));

// Test
echo Doctrine::getTable('Record')->createQuery()->select('id')->whereIn('id', array())->getSqlQuery() , "\n";
echo Doctrine::getTable('Record')->createQuery()->select('id')->whereIn('id', array())->fetchArray() , "\n";

// Result is:
// SELECT r.id AS r__id FROM record r
// Array