Relate objects and objectrelationlist

Next topic

Author	Message
Roy Bøhmer	Sunday 24 October 2004 6:49:18 am Hi! As far as I know there are two documented ways to relate objects to each other: 1) the datatype 'ezKeywords' 2) the function 'related objects' Both has some major disadvantages. The keywords is a great feature, but with several authors the list list of keywords will soon grow confusingly large. You could also make a list of legal keywords, but it's still volunerable for typos. The related objects is also great, but because it's used to insert images etc. into xmltxt you loose some control of what content should be listed as related content/downloadable files etc. and what should not. I've gone public with one site using ezObjectrelationlist (ORL) to do the relation. Later I found this to have some major drawbacks too: When two objects both put the each other in ORL the server times out when saving. (some kind of never ending circle resulting in many entires in ORL – all of the same object.) In addition, when an object is deleted its not deleted from the ORLs its in. Have I missed something? I use ORL a lot for selecting topstoies etc, but I start wondering if I don't understand the inner working of that datatype. Anyone have an explanation on how ORL stores its data? How would you do "the perfect" relation of relating content? Roy B

Author

Message

Sunday 24 October 2004 6:49:18 am

Hi!

As far as I know there are two documented ways to relate objects to each other:
1) the datatype 'ezKeywords'
2) the function 'related objects'

Both has some major disadvantages.
The keywords is a great feature, but with several authors the list list of keywords will soon grow confusingly large. You could also make a list of legal keywords, but it's still volunerable for typos.
The related objects is also great, but because it's used to insert images etc. into xmltxt you loose some control of what content should be listed as related content/downloadable files etc. and what should not.

I've gone public with one site using ezObjectrelationlist (ORL) to do the relation. Later I found this to have some major drawbacks too: When two objects both put the each other in ORL the server times out when saving. (some kind of never ending circle resulting in many entires in ORL – all of the same object.) In addition, when an object is deleted its not deleted from the ORLs its in.

Have I missed something?
I use ORL a lot for selecting topstoies etc, but I start wondering if I don't understand the inner working of that datatype. Anyone have an explanation on how ORL stores its data?

How would you do "the perfect" relation of relating content?

Roy B

eZ debug

Timing:	Jan 19 2025 07:16:07
Script start
Timing:	Jan 19 2025 07:16:07
Module start 'layout'
Timing:	Jan 19 2025 07:16:07
Module start 'content'
Timing:	Jan 19 2025 07:16:07
Module end 'content'
Timing:	Jan 19 2025 07:16:07
Script end

Main resources:

Total runtime	0.0140 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.0053	589.1719	152.6250
Module start 'layout'	0.0053	0.0020	741.7969	39.4453
Module start 'content'	0.0072	0.0048	781.2422	85.1953
Module end 'content'	0.0120	0.0019	866.4375	30.3047
Script end	0.0139		896.7422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	16.5652	14	0.0002
Check MTime	0.0010	7.3737	14	0.0001
Mysql Total
Database connection	0.0007	5.3359	1	0.0007
Mysqli_queries	0.0022	15.4568	3	0.0007
Looping result	0.0000	0.0648	1	0.0000
Template Total	0.0016	11.6	1	0.0016
Template load	0.0008	6.0214	1	0.0008
Template processing	0.0008	5.5934	1	0.0008
Override
Cache load	0.0006	4.2922	1	0.0006
General
dbfile	0.0011	7.8341	8	0.0001
String conversion	0.0000	0.0290	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