Object relation list vs related items

«

Previous topic

|

|

Next topic

»

Author	Message
Daniel Guerrier	Tuesday 29 March 2005 9:32:36 am Is there any advantage or disadvantage between relating objects in the content class using the object relation datatype and relating object thru the interface. If use the latter, how do I get a list of related items.
Xavier Dutoit	Wednesday 30 March 2005 1:10:49 am Hi fighter ;) The advantage of the related object is that you can find the reverse relations (find all the objects that they they are related to me). Have a look at my contrib: http://ez.no/community/contribs/datatypes/enhanced_objectrelation It allows both to have a nice list display for the selection and store it has a real object relation. Xavier http://www.sydesy.com
Łukasz Serwatka	Wednesday 30 March 2005 1:18:21 am Difference depends on the usage. The related objects list on the bottom (relating object thru the interface) is really meant for general related objects through the XML fields. If you have specific related objects you should use a datatype since this gives you more control. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Stefano Guandalini	Monday 03 October 2005 3:29:14 am This is very nice, but is there any way to know if an object is pointed to, from a relation that is stored in a datatype, as for the reverse related object list? Thank you. Bye Stefano Guandalini http://www.nizan.net
Xavier Dutoit	Monday 03 October 2005 6:07:18 am Actally, eor uses the same table than the standard object relation. You can use all the standard features to fetch related (and reverse related) objects. http://ez.no/community/contribs/datatypes/enhanced_objectrelation http://www.sydesy.com

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 01:15:42
Script start
Timing:	Jan 31 2025 01:15:42
Module start 'layout'
Timing:	Jan 31 2025 01:15:42
Module start 'content'
Timing:	Jan 31 2025 01:15:42
Module end 'content'
Timing:	Jan 31 2025 01:15:42
Script end

Main resources:

Total runtime	0.0325 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0061	588.2578	151.2266
Module start 'layout'	0.0062	0.0058	739.4844	220.7188
Module start 'content'	0.0120	0.0184	960.2031	1,001.7109
Module end 'content'	0.0304	0.0021	1,961.9141	33.9922
Script end	0.0325		1,995.9063

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	9.2581	14	0.0002
Check MTime	0.0012	3.6294	14	0.0001
Mysql Total
Database connection	0.0012	3.6610	1	0.0012
Mysqli_queries	0.0030	9.1414	3	0.0010
Looping result	0.0000	0.0983	1	0.0000
Template Total	0.0016	4.9	1	0.0016
Template load	0.0012	3.5964	1	0.0012
Template processing	0.0004	1.2702	1	0.0004
Override
Cache load	0.0007	2.2639	1	0.0007
General
dbfile	0.0019	5.7547	8	0.0002
String conversion	0.0000	0.0345	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