eZ-Crew: Please advise; RC's and lunacy

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Atle Enersen	Thursday 06 February 2003 11:52:24 pm koff A release-candidate would normally be close-to-final especially regarding database-structures and major functionality. Well, this is not the case regarding RC1 <--> RC2. Lucky me only has a small site running on RC1 (which I tried to convert to RC2 yesterday with no luck), but it could have been devestating if it was a large site. I did not dig deep into why the conversion RC1 -> RC2 did not work because the site is small and ends it's lifecycle mid april. Q: WIll there be major changes RC2 -> Rel/RC3? We are planning to use eZp on several sites, and since one of them are of commercial type actually buy a license :-) However - if there is the sligthest possibility of major changes like RC1 -> RC2 wee cannot start migrating... Please advise... \atle\ --
Bård Farstad	Friday 07 February 2003 12:11:49 am There are changes in the database between RC1 and RC2. These changes are 100% upgradable and are added because of problems discovered during testing. You can find the database upgrade script at: http://zev.ez.no/svn/nextgen/trunk/database_update.sql Upgrade run all the SQL commands after the comment # After RC1 After running the SQL commands you should have no problems in using an RC-1 database, or older. --bård Documentation: http://ez.no/doc
Atle Enersen	Friday 07 February 2003 12:22:22 am > You can find the database upgrade script at: > http://zev.ez.no/svn/nextgen/trunk/database_update.sql > Upgrade run all the SQL commands after the comment > # After RC1 > After running the SQL commands you should have no problems > in using an RC-1 database, or older. Well... It did not work yesterday. I will try again later today. \atle\ --
Brendan Pike	Friday 07 February 2003 6:54:09 am I also tried the upgrade sql script but it failed. I tried in both shell and phpMyAdmin but got the same error: ERROR 1060 at line 3: Duplicate column name 'sort_field' It worked in windows however so I'll dump the database and take a copy of the windows upgraded one. Cheers Brendan www.dbinformatics.com.au We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.

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 18 2025 11:21:51
Script start
Timing:	Jan 18 2025 11:21:51
Module start 'layout'
Timing:	Jan 18 2025 11:21:51
Module start 'content'
Timing:	Jan 18 2025 11:21:51
Module end 'content'
Timing:	Jan 18 2025 11:21:51
Script end

Main resources:

Total runtime	0.0247 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.0068	589.1719	152.6406
Module start 'layout'	0.0068	0.0033	741.8125	39.4922
Module start 'content'	0.0101	0.0111	781.3047	93.3672
Module end 'content'	0.0212	0.0034	874.6719	34.3047
Script end	0.0246		908.9766

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	11.5844	14	0.0002
Check MTime	0.0011	4.6349	14	0.0001
Mysql Total
Database connection	0.0011	4.3601	1	0.0011
Mysqli_queries	0.0029	11.6384	3	0.0010
Looping result	0.0000	0.0694	1	0.0000
Template Total	0.0028	11.3	1	0.0028
Template load	0.0014	5.5135	1	0.0014
Template processing	0.0014	5.7160	1	0.0014
Override
Cache load	0.0008	3.2115	1	0.0008
General
dbfile	0.0021	8.3276	8	0.0003
String conversion	0.0000	0.0328	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.0002 secs