Howto import objects if a large object structure is deleted?

Next topic

Author	Message
K259	Friday 08 July 2005 1:53:53 am We have 5 sections on our site. Every section is assigned to a place in the structure and every section has thousands of objects. If our users deletes some object in the structure which contains a large number of objects then every object loses it's relation and must be restored from the trashcan one and one. This is not realistic to do, it will take days, so I need to import this deleted structure into the db from the mysql-backup. Does eZ or others have a finished solution on this, a script which will solve this problem?
Gabriel Ambuehl	Saturday 30 July 2005 7:06:43 am You could always stop users from deleting things. Or export your content to ezpackages every once in a while. But restoring from earlier SQL dumps seems like asking for trouble to me. Visit http://triligon.org
K259	Sunday 31 July 2005 12:08:59 pm How do I export content under a node to a package, and how do I import it?

Author

Message

Friday 08 July 2005 1:53:53 am

We have 5 sections on our site. Every section is assigned to a place in the structure and every section has thousands of objects.

If our users deletes some object in the structure which contains a large number of objects then every object loses it's relation and must be restored from the trashcan one and one.

This is not realistic to do, it will take days, so I need to import this deleted structure into the db from the mysql-backup.

Does eZ or others have a finished solution on this, a script which will solve this problem?

Gabriel Ambuehl

Saturday 30 July 2005 7:06:43 am

You could always stop users from deleting things.

Or export your content to ezpackages every once in a while.

But restoring from earlier SQL dumps seems like asking for trouble to me.

Visit http://triligon.org

K259

Sunday 31 July 2005 12:08:59 pm

How do I export content under a node to a package, and how do I import it?

eZ debug

Timing:	Jan 31 2025 06:17:58
Script start
Timing:	Jan 31 2025 06:17:58
Module start 'layout'
Timing:	Jan 31 2025 06:17:58
Module start 'content'
Timing:	Jan 31 2025 06:17:58
Module end 'content'
Timing:	Jan 31 2025 06:17:58
Script end

Main resources:

Total runtime	0.0188 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.0087	588.3906	151.2422
Module start 'layout'	0.0087	0.0036	739.6328	36.7109
Module start 'content'	0.0123	0.0049	776.3438	90.0156
Module end 'content'	0.0171	0.0016	866.3594	29.9922
Script end	0.0188		896.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	13.2505	14	0.0002
Check MTime	0.0012	6.2501	14	0.0001
Mysql Total
Database connection	0.0011	5.6886	1	0.0011
Mysqli_queries	0.0052	27.8421	3	0.0017
Looping result	0.0000	0.1115	1	0.0000
Template Total	0.0012	6.6	1	0.0012
Template load	0.0009	5.0244	1	0.0009
Template processing	0.0003	1.5197	1	0.0003
Override
Cache load	0.0007	3.5148	1	0.0007
General
dbfile	0.0014	7.2324	8	0.0002
String conversion	0.0000	0.1660	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