#460: support for composite keys relations
--------------------------+-------------------------------------------------
  Reporter:  mahono       |       Owner:  romanb                 
      Type:  enhancement  |      Status:  new                    
  Priority:  critical     |   Milestone:  2.0.0                  
 Component:  Other        |     Version:                         
Resolution:               |    Keywords:  composite keys relation
  Has_test:  0            |    Mystatus:  Pending Core Response  
 Has_patch:  0            |  
--------------------------+-------------------------------------------------
Old description:

> (My apologize to mahono: I accidentally wiped your description when I
> wanted to add a comment, and didn't find any way to revert it. -- tamcy)
>
> This ticket is about, as the subject tells, supporting composite key
> relations, and proposed with the following syntax:
>
> {{{
> array('local' => array('col_a', 'col_b'), 'foreign' => array('col_a',
> 'col_b'));
> }}}

New description:

 I am also woting for this feature.

  I need this with i18n and database performance, where I can't handle all
  data in one table, and I need to split it into two tables for example:
  {{{
  stNodeTranslation:
    columns:
      id:
        type: integer(11)
        primary: true
      lang:
        type: string(2)
        primary: true
      title: string(255)
      teaser: string(1000)
      published_from: timestamp
      published_to:   timestamp
      is_published:   boolean
    relations:
      storage:
        class: stNodeTranslationStorage
        foreign: [id, lang]
        local:   [id, lang]
        type:    one

  stNodeTranslationStorage:
    columns:
      id:
        type: integer(11)
        primary: true
      lang:
        type: string(2)
        primary: true
      body: clob
      other_big_column: clob
  }}}

  I need to split it because in first table are columns that are heavily
  used in various lists with some full table scans and putting large unused
  columns reduced the size of the scanned table, so the scans run faster.
 So
  if I can use relations on two columns it would be great. Now I'am writing
  own queries to "simulate" this behavior.

-- 
Ticket URL: <http://trac.doctrine-project.org/ticket/460#comment:13>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"doctrine-svn" group.
 To post to this group, send email to [email protected]
 To unsubscribe from this group, send email to [EMAIL PROTECTED]
 For more options, visit this group at 
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---

Reply via email to