search in sub objects

Next topic

Author	Message
Aladdin Mouhaimeed	Friday 26 August 2005 9:07:46 am This is maybe my last unknown stuff on my way to build my site using eZ Publish. I want my users profile to contain many sub objects. For example: Resume, Skills, etc.. I simply make the relationship by making the user node a parent of the sub object, and when showing the profile I show all the child objects (the sub objects). I don’t know if using related object attributes would be better. Anyway, Now I want to make my advanced search on users. My search will be on attributes of the sub objects. For example the visitor will chose a value of some child object attribute like: Skill->degree, and another value: Resume->domain, and then I will fetch all users whose sub objects match these two values. I tried my best searching all search documents but find no answer. If necessary I can review the structure of relating my objects, and use whatever suitable structure to get that search functionality. Make any sense to you out there? Any hints would be greatly appreciated!! Thanks --
Aladdin Mouhaimeed	Friday 26 August 2005 1:17:17 pm Well, I know it is not an easy stuff, and frankly, I dout that I may have an answer at all, but I hope that ez crew guys may have a hint or an advice, I will wait.

Author

Message

Friday 26 August 2005 9:07:46 am

This is maybe my last unknown stuff on my way to build my site using eZ Publish.

I want my users profile to contain many sub objects. For example: Resume, Skills, etc..
I simply make the relationship by making the user node a parent of the sub object, and when showing the profile I show all the child objects (the sub objects).
I don’t know if using related object attributes would be better.

Anyway,
Now I want to make my advanced search on users.
My search will be on attributes of the sub objects. For example the visitor will chose a value of some child object attribute like: Skill->degree, and another value: Resume->domain, and then I will fetch all users whose sub objects match these two values.

I tried my best searching all search documents but find no answer.

If necessary I can review the structure of relating my objects, and use whatever suitable structure to get that search functionality.

Make any sense to you out there? Any hints would be greatly appreciated!!
Thanks --

Aladdin Mouhaimeed

Friday 26 August 2005 1:17:17 pm

Well,
I know it is not an easy stuff,
and frankly, I dout that I may have an answer at all,
but I hope that ez crew guys may have a hint or an advice,
I will wait.

eZ debug

Timing:	Jan 18 2025 22:23:54
Script start
Timing:	Jan 18 2025 22:23:54
Module start 'layout'
Timing:	Jan 18 2025 22:23:54
Module start 'content'
Timing:	Jan 18 2025 22:23:54
Module end 'content'
Timing:	Jan 18 2025 22:23:54
Script end

Main resources:

Total runtime	0.0143 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0046	587.8906	152.6094
Module start 'layout'	0.0046	0.0030	740.5000	39.4141
Module start 'content'	0.0076	0.0049	779.9141	89.1953
Module end 'content'	0.0125	0.0018	869.1094	30.3047
Script end	0.0143		899.4141

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.4709	14	0.0002
Check MTime	0.0011	7.7982	14	0.0001
Mysql Total
Database connection	0.0005	3.8365	1	0.0005
Mysqli_queries	0.0025	17.4371	3	0.0008
Looping result	0.0000	0.0901	1	0.0000
Template Total	0.0014	10.1	1	0.0014
Template load	0.0008	5.5220	1	0.0008
Template processing	0.0006	4.5007	1	0.0006
Override
Cache load	0.0005	3.7514	1	0.0005
General
dbfile	0.0003	2.1477	8	0.0000
String conversion	0.0000	0.0668	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs