Supporting Composite Primary Keys for ActiveRecord

[oddz]

Which one of these make for a better interface when initiating the ActiveRecord finder through object instantiation?

/* 
* 1 maps to first key in primary key array
* 2 maps to second  in primary key array
*/
new BlogCategory(1,5); 

/*
* mock named parameters so order isn't required
*/
new BlogCategory('blog_id:1','category_id:5');

or

new BlogCategory('category_id:5','blog_id:1'); 

Simple Model Definition:

class BlogCategory extends ActiveRecord {
     public static $primaryKey = array('blog_id','category_id');
     public static $foreignKeys = array(
          'blog_id'=>'Blog'
          ,'category_id'=>'Category'
     );
} 

I like the first for its simplicity, but then the primary key "order" must be remembered. The second is much more flexible, but yields a more complex interface.

Any other ideas?

thx

[Mastodont]

Any other ideas?
Yes - do not use AR for M:N relation binding table ... Do you really need extra AR for finder?

[XtrEM3]

i agree. instead, use AR for Blog, or even Category which will contain multiple Blogs through the BlogCategory relationship table.

edit: but to answer your question, if i had to pick, i'd go with your first approach. the second seems less elegant, partially because you lose your type enforcement, which -- using java often -- i'm a fan of.

[allspiritseve]

Which one of these make for a better interface when initiating the ActiveRecord finder through object instantiation?

Either the first example, or:

new BlogCategory(array(1, 5)); 

[Czaries]

Or you could do something like this, to match the definition:

new BlogCategory(array('blog_id' => 1, 'cateogry_id' => 5));