In which case do I need to update the database ?

Author Message

Nabil Alimi

Friday 24 June 2005 8:33:29 am

Hi,

Here's my situation.
I work on an ezpublish site on my comp' (local then). There's also an online version and an other person is adding content to it .But the site is not complete yet, so I still have to make functoinal changes.
As database updates are a bit troublesome and as I think I dont need to update it every time I change something in the site, I'd like to know what requires database updates.

Thanks for reading me.

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr

Paul Borgermans

Friday 24 June 2005 9:44:31 am

Nabil, what do you mean by functional changes?

Anyway, if you mean things done in the admin interface most of the time update the underlying database (example: content, classes, roles and policies, ...)

Only ini settings and templates do not reside in the database ...

If you have content out of sync between your local and live site, you can use object export and import, class export and import but that's all. In the 4.x series, there will probably much more to import/export.

Do not try to update the dabase yourself, you will probably corrupt it as the ezp database design is heavily normalised.

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Nabil Alimi

Monday 27 June 2005 5:04:28 am

I meant changing classes, adding new ones etc... Everything that is not content related.

But I somehow have my answer.
Thanks Paul.

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr

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:16:25
Script start
Timing: Jan 31 2025 01:16:25
Module start 'layout'
Timing: Jan 31 2025 01:16:25
Module start 'content'
Timing: Jan 31 2025 01:16:25
Module end 'content'
Timing: Jan 31 2025 01:16:25
Script end

Main resources:

Total runtime0.0234 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0042 588.2656151.2266
Module start 'layout' 0.00420.0038 739.4922220.7188
Module start 'content' 0.00800.0140 960.21091,001.8359
Module end 'content' 0.02200.0014 1,962.046933.9922
Script end 0.0234  1,996.0391 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002610.9654140.0002
Check MTime0.00114.5368140.0001
Mysql Total
Database connection0.00062.612410.0006
Mysqli_queries0.00208.648530.0007
Looping result0.00000.056110.0000
Template Total0.00104.410.0010
Template load0.00083.510410.0008
Template processing0.00020.906110.0002
Override
Cache load0.00062.355510.0006
General
dbfile0.00187.586580.0002
String conversion0.00000.037740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs