|
From: Ulf E. <ulf...@fa...> - 2005-03-01 19:25:40
|
* Benjamin Curtis [2005-02-24 16:21]: > > Ulf Erikson wrote: >>Do you mind if I suggest more blockers? ;-) The earlier security issue >>should probably be revisited once more, and considering the speed of >>development it would probably be a very good idea to make sure that both >>php5 and MySQL 4.1 are possible platforms for phpBugTracker 1.0. >> > > > Heh, sure, more blockers are always fun. Yes, the security issues need > to be reviewed again, and I can vote for PHP5 support. I'm not sure > about MySQL 4.1, though, as I had some problems with it combined with > transaction support while trying to use adodb. Of course, I probably > just didn't spend enough time on it to nail down the exact problem. :) This is the only issue I have had with PHP5: http://sourceforge.net/mailarchive/forum.php?thread_id=6535282&forum_id=4570 Basically get_class() no longer returns a string with only lowercase characters. Simply use DB::isError in your own code, and make sure to update PEAR to have a functional isError. (the one i tried used is_a(), but that function still couldn't handle it) If nothing else helps, how about renaming all "DB_Error" to "db_error" such that all old tests still work? What problems do you think phpBugTracker will have with MySQL 4.1? (and how is ADOdb related?) I assumed that using myqsli.php instead of mysql.php would take care of all API changes. The big bulk of old queries must still be valid. or.. ? -- Ulf |