How can I find the table in the database

Next topic

Author	Message
Fiona Hisa	Friday 08 December 2006 12:54:17 am I just want to ask that if I create a class and a object of it ,How can I find the table which store the information of the object ?If there is any configuration file can tell me? the tables are too much!! thank you ! my English is poor ,may you can understand! ^_^
Kristof Coomans	Friday 08 December 2006 1:54:34 am Hello Susan, welcome to the eZ community! Unfortunately something went wrong with my previous reply, so I'll have to type it again. You can find a database diagram at http://ez.no/ezpublish/documentation/reference/database_diagram. It's outdated but it's a start. Content objects are using a lot of database tables, the most important ones are: ezcontentobject ezcontentobject_version ezcontentobject_attribute Others are: ezcontentobject_link ezcontentobject_name eznodeassignment ezcontentobject_tree Some datatypes use other tables as well. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Fiona Hisa	Tuesday 12 December 2006 9:31:58 pm hehe, thank you very much ,I just a begginer of the eZ publish ,so there's a lot of questions. I feel this software is very well,I will study hard.ha.

Author

Message

Friday 08 December 2006 12:54:17 am

I just want to ask that if I create a class and a object of it ,How can I find the table which store
the information of the object ?If there is any configuration file can tell me?
the tables are too much!!
thank you !
my English is poor ,may you can understand! ^_^

Kristof Coomans

Friday 08 December 2006 1:54:34 am

Hello Susan, welcome to the eZ community!

Unfortunately something went wrong with my previous reply, so I'll have to type it again.

You can find a database diagram at http://ez.no/ezpublish/documentation/reference/database_diagram. It's outdated but it's a start.

Content objects are using a lot of database tables, the most important ones are:

ezcontentobject
ezcontentobject_version
ezcontentobject_attribute

Others are:

ezcontentobject_link
ezcontentobject_name
eznodeassignment
ezcontentobject_tree

Some datatypes use other tables as well.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Fiona Hisa

Tuesday 12 December 2006 9:31:58 pm

hehe, thank you very much ,I just a begginer of the eZ publish ,so there's a lot of questions.
I feel this software is very well,I will study hard.ha.

eZ debug

Timing:	Jan 30 2025 21:38:38
Script start
Timing:	Jan 30 2025 21:38:38
Module start 'layout'
Timing:	Jan 30 2025 21:38:38
Module start 'content'
Timing:	Jan 30 2025 21:38:38
Module end 'content'
Timing:	Jan 30 2025 21:38:38
Script end

Main resources:

Total runtime	0.0286 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.0052	588.2656	151.2266
Module start 'layout'	0.0052	0.0046	739.4922	220.7188
Module start 'content'	0.0098	0.0172	960.2109	997.8359
Module end 'content'	0.0270	0.0016	1,958.0469	29.9922
Script end	0.0286		1,988.0391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	10.2661	14	0.0002
Check MTime	0.0011	4.0112	14	0.0001
Mysql Total
Database connection	0.0007	2.5058	1	0.0007
Mysqli_queries	0.0028	9.6236	3	0.0009
Looping result	0.0000	0.0832	1	0.0000
Template Total	0.0011	3.9	1	0.0011
Template load	0.0009	3.0509	1	0.0009
Template processing	0.0002	0.8272	1	0.0002
Override
Cache load	0.0006	2.0239	1	0.0006
General
dbfile	0.0025	8.8646	8	0.0003
String conversion	0.0000	0.0391	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