MySQL vs MySQLi (improved)

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Piotrek Karaś	Monday 03 December 2007 10:30:32 pm Hello there, Can anyone comment on the differences between mysql and mysql improved library for mysql in the context of eZ Publish? Especially: 1) What would be the strengths of one over other for eZ in particular? 2) Is there ANY greater risk of coming across a bug (simply because mysqli hadn't been introduced until recently)? Or is it totally transparent, or some kind of abstraction layer takes care of differences? 3) If my hosting environment provides both for PHP5, would it be for any reason not recommended to switch between both options later on, having some content in? Thanks for any suggestions, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Jonny Bergkvist	Wednesday 30 January 2008 6:10:28 am Hello, The documentation page: http://ez.no/doc/ez_publish/technical_manual/4_0/installation/the_setup_wizard Says the following: " Note that if the MySQLi extension is enabled in PHP, the "MySQL Improved" option will be available on the list. If you are going to use a MySQL database, it is recommended to select "MySQL Improved" instead of "MySQL". " As Piotrek asks for, it would be great with some details of the difference between using mysql vs. mysqli in the context of eZp 4. If you know, please share your information here :-) Thanks, Jonny
Björn Dieding@xrow.de	Wednesday 30 January 2008 4:30:27 pm http://www.php.net/mysqli I can just point you to this url... As you can see it is kind of a software/driver upgrade with new functionality. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Piotrek Karaś	Wednesday 30 January 2008 5:13:29 pm Yup, I had already dealt with it before I first touched eZ Publish. Just thought there could be some eZ related issues. How would you see lack of persistent connections for an eZ site with high traffic? Did actually eZ Publish make use of those at all? Thanks -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Martin Burger	Sunday 09 August 2009 1:48:50 am Especially this page provides further information: http://www.php.net/manual/en/mysqli.overview.php They advise to use MySQLi: "Note: If you are using MySQL versions 4.1.3 or later it is strongly recommended that you use this extension. " http://www.netbeyond.de/
Gaetano Giunta	Monday 10 August 2009 1:02:58 am As for eZP-specifics, some corner cases are: - cluster-mode support still lacking - script to convert db from mysqli to oracle still lacking Principal Consultant International Business Member of the Community Project Board
Piotrek Karaś	Monday 10 August 2009 1:15:13 am Now, that's piece of concrete and practical info, Gaetano. Thanks! I think this could be mentioned somewhere, for example in the installation wizard. Cheers, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

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

Main resources:

Total runtime	0.0145 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.0050	587.9375	152.6250
Module start 'layout'	0.0050	0.0029	740.5625	39.4453
Module start 'content'	0.0079	0.0043	780.0078	101.3516
Module end 'content'	0.0122	0.0022	881.3594	42.3047
Script end	0.0144		923.6641

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.7500	14	0.0002
Check MTime	0.0012	8.1101	14	0.0001
Mysql Total
Database connection	0.0008	5.2784	1	0.0008
Mysqli_queries	0.0025	16.9343	3	0.0008
Looping result	0.0000	0.1728	1	0.0000
Template Total	0.0019	13.1	1	0.0019
Template load	0.0010	6.9090	1	0.0010
Template processing	0.0009	6.1899	1	0.0009
Override
Cache load	0.0007	5.0579	1	0.0007
General
dbfile	0.0002	1.3229	8	0.0000
String conversion	0.0000	0.0691	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