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 1.0-rc7
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Lucas K - 10.08.2018
Last edited by peterdd - 10.08.2018

FS#2477 - old style MySQL extension is abandoned ..

the old php mysql extension is long ago reached its demise, why bother supporting it?

I also see in the database connector that your supporting MySQL/PDO - why not settle on that? If the queries aren’t MySQL specific, it becomes easier to support other DB’s, etc.

Project Manager
peterdd commented on 10.08.2018 11:10

Why bother supporting old mysql extension: ADOdb still supports it and ADOdb and Flyspray support also older PHP versions. So no urgent reason yet to drop and other stuff has higher priority.

Adding the pdo_mysql driver code part to includes/class.database.inc.php is just experimental and added by me as an example. The problem is, that the 'drivers' of ADOdb are not equal in features and quality (as they should) and the xmlschema03 install and upgrades must result consistently in same quality results for each db connection type it official supports. Even for postgresql comes with our own setup/upgrade/1.0/datadict-postgres.inc.php file that patches ADOdb. Thats why I'm currently focusing on pushing/improving ADOdb project https://github.com/ADOdb/ADOdb for cross db tests.

That is also the reason I do 1.0-rcX releases instead 1.0.1, 1.0.2, .. releases. Just fear to break with the, must get confidence with tests before doing setup/upgrade/1.0.1 directory.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing