|
Wednesday 19 December 2007 12:51:04 am
Xavier,
<i>You have the same fetching tools on related objects as you have on keywords, isn't it ?</i>
When it comes to core eZ API - yes. But if you want to operate on data directly (even if just for reads) than keywords seem much more efficient. However, I haven't studied the object relations' database architecture yet, it might be that I'm wrong. I'll try to confirm that soon.
<i>As for the input form (comma separated), my users are "creative' enough so I can be sure that any of them won't choose the same keyword but a slightly different one (typo included)</i>
I believe this is another important issue that you touched, but not necessarily directly related one. If you want to force quality check, than object relations would be a much better choice, but then it would be a closed system (unless I don't see something). On the other hand, as you say - keywords are very risky to be given away to public because of problem you described. But they do great when it comes to a system with content quality enforced outside of eZ Publish. And I believe they could do much better with additional key ;) Piotrek
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|