Idea Database problem with mysql instead of mysqli

I just installed Kunena a few days ago and it has an impressive feature set.

However, I found one issue which is really bugging me. My page uses mysql by default, but I found that I get Kunena db errors unless I switch to mysqli. Reading about the differences between mysql and mysqli on the Joomla forum I am finding that Joomla recommends to use mysql.

Is this a release candidate problem or did I miss a Kunena setting somewhere?

Thanks,
Jens

mysqli and mysql are the same thing, mysqli stands for " MySQL Improved Extension "

FYI: The mysqli extension allows you to access the functionality provided by MySQL 4.1 and above. More information about the MySQL Database server can be found at » www.mysql.com/

Documentation for MySQL can be found at » dev.mysql.com/doc/ .

Parts of this documentation included from MySQL manual with permissions of Oracle Corporation.

mysqli and mysql are the same thing??? There is some story:

Released together with PHP 5, the MySQLi extension aimed to replace the old, reliable MySQL extension which has been available in PHP since the mid-90s. After almost a decade of development activities some questionable features had crept into ext/mysql. The extension became difficult to maintain and the feature set of ext/mysql started to differ from that of the underlying MySQL client library.

At this point, Georg Richter made a clear cut and developed the MySQLi extension. The "i" in the name of the extension stands for: improved, interface, incomplete or whatever you want to call it.

The new extension ext/mysqli supports all new features of the MySQL Server Version 4.1 and higher, for example Prepared Statements and support for Character Sets. Prepared statements are a great step ahead, especially nowadays when everybody is concerned about security.

The MySQLi extension has a procedural interface which is very similar to the ext/mysql interface to make porting as simple as possible and it offers an additional object oriented interface for those who prefer the object oriented programming style.

The new features are the reason why you should switch to PHP 5 and ext/mysqli, if you have not done this step yet. Looking forward at PHP 6, we do not plan to add Unicode to the old PHP MySQL extension The feature set of the old extension is not state of the art any more, even with Unicode support.

yep just like kunena used to be called fireboard ( sry devs but that was best comparison i could think of )

jstraten wrote: I just installed Kunena a few days ago and it has an impressive feature set.

However, I found one issue which is really bugging me. My page uses mysql by default, but I found that I get Kunena db errors unless I switch to mysqli. Reading about the differences between mysql and mysqli on the Joomla forum I am finding that Joomla recommends to use mysql.

Is this a release candidate problem or did I miss a Kunena setting somewhere?

Thanks,
Jens

Aside from the mysql vs mysqli discussion: What are the errors you are seeing. We have not planned to make mysqli a requirement - although I have to say that I have been using it on all my sites for years.

Thank you for all the feedback.

I personally don't have any preference for mysql or mysqli, but from postings in various other forums I was under the impression that mysqli has been discontinued and that it wouldn't be available in PHP 6 anymore. That's the reason why my pages are currently using mysql.

If that is not the case, I am totally fine with switching to mysqli.

fxstein, when I use mysql, I am seeing the following error messages all over the page:

The Joomla log itself shows no errors, but it appears that Kunena has problems accessing the db.

Thanks,
Jens