You will likely not need to define your own SQL for most tasks. If you need to, you'll most likely have to write an extension (possibly template operator) and that does need PHP knowledge.
Well, most likely I will need to define my own SQL queries, because there will be a lot of non-ezPublish tables which I'll have to search. So probably there's no easy way to incorporate custom php scripts and pass their results to ezP templates?
I know, that I can create extension/module but - according to this: http://ez.no/products/ez_publish_cms/documentation/development/extensions/module/module_tutorial_part_1 do I really need to create such complicated structure and fuctions to extract data from non-ezP tables?
I know, that I can create extension/module but - according to this: http://ez.no/products/ez_publish_...nsions/module/module_tutorial_part_1
do I really need to create such complicated structure and fuctions to extract data from non-ezP tables?
While it may seem complicated once you get your head around it you will find that most of the functions you require are provided by eZ.
Also look at the eZPersistentObject class http://pubsvn.ez.no/doxygen/classeZPersistentObject.html
The fact that functions are provided by eZ doesn't necessarily mean it's easier. In some case one could truly argue it to be much harder if you try to use the integrated API as opposed to just firing SQL against the DB...
The fact that functions are provided by eZ doesn't necessarily mean it's easier. In some case one could truly argue it to be much harder if you try to use the integrated API as opposed to just firing SQL against the DB...
Sure and sometimes you have to do that. It all depends on what you need to do and how complex that database structure is.
What I was pointing out is that the eZ framework provides a lot of functionality that if used can save a lot of time. It may seem complicated on the surface but once you get used to using it, it can be quite simple*.
