Flyspray - The bug killer!

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Information
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 0.9.9.7
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Shane Hollis - 10.10.2015
Last edited by peterdd - 17.10.2015

FS#2068 - Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future

My version of PHP still shows deprecation warnings with flyspray.

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /var/www/flyspray.itiab.co.nz/htdocs/adodb/drivers/adodb-mysql.inc.php on line 353

Have all mysql.connect instances been removed? The connect will be removed from PHP soon and will cause problems.

Project Manager
peterdd commented on 10.10.2015 05:55

Have you tried to change it to

dbtype="mysqli"

in flyspray.conf.php?

@all: Should we consider this at upgrades and give option to users to change their old setting from mysql to mysqli driver?

Shane Hollis commented on 10.10.2015 07:04

The PDO connection api could be considered too.

A comparison of them both here:
http://blog.ulf-wendel.de/2012/php-mysql-why-to-upgrade-extmysql/

Good to see what fits best.

Shane Hollis commented on 10.10.2015 07:07

Altered connection as per your suggestion - logged in - no message.

Thanks

David commented on 23.11.2015 10:13

I got the same thing after upgrading my version of PHP. Followed the above to change the DB type and it worked.

Jehan commented on 07.12.2015 01:41

I got the same error. It indeed gets away when changing to mysqli driver.
If the "mysql" one is deprecated, meant to disappear and "mysqli" does the job, is there any reason to keep it around?

Project Manager
peterdd commented on 07.12.2015 11:38

Yeah, we should handle this during upgrade process in future. (Check if mysqli extension is available/active and if yes change from mysql to mysqli)

I hesitated to remove the 'mysql'-option because it could be that on an old web/local hosting the mysql extension could be active but not the 'mysqli'. But maybe this is quite ancient now after all that long time of deprecated 'mysql'-extension..

Jehan commented on 08.12.2015 20:09

Maybe you could keep "mysql", but put a big red warning next to it saying something like "mysql extension is deprecated, will likely output PHP warnings with a recent PHP version and support may be dropped in the future by Flyspray. Use mysqli instead". Or something like this.

At least, it spares us wasted time when we don't know. When both are presented side by side, the same way, I had no idea that one was deprecated, so I choose randomly.

I think if you just make it clear during install that "mysql" support is deprecated and only kept for compatibility with old web servers and should be avoided when possible, or what not, then it's ok to keep it, I guess.

No time wasted for the common user with recent versions, and users with special (old) needs stay happy too.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing