[eluser]mcnux[/eluser]
[quote author="OverZealous" date="1251324145"]
DMZ is checking correctly. You've just got the wrong name for your column. :-)
If the relationship is called 'list_item', then the in-table foreign key column is called 'list_item_id'.
[/quote]
I think what you meant to say was as the model is called 'base_list', the ITFK on list_item should be called 'base_list_id'.
[quote author="OverZealous" date="1251324145"]
DMZ always uses the relationship key (which is usually the class name) for determining ITFK names. Otherwise, you couldn't have more than one relationship to the same object.
[/quote]
Hmm. Isn't it more important to be able to name your models differently to your tables? Especially for single table inheritance, for example. I was expecting the model to map correctly because I've specified a different table name. I would have thought to specify different foreign keys than the table name would be a further modification.
I understand how the foreign keys for relationships can be customised to account for multiple foreign keys to the same model but I think being able to have differing model names is a separate issue.
[quote author="OverZealous" date="1251324145"]
FYI: If you aren't working with advanced relationships (where you need to specify a class name, etc.), you don't need to include the empty array in your $has_one or $has_many properties.[/quote]
Thanks yeah I just wanted to keep them all the same.