Sunday, 2010-12-26

dhx1breaking in 3...2...1...00:58
CIA-27Mantisbt: hickseydr * r49aac093ce6a / (54 files in 5 dirs): Issue #12545: Replace deprecated <b> tags with <strong>00:58
CIA-27Mantisbt: hickseydr * r6f0f5930d3f0 /account_sponsor_page.php: Issue #12545: Remove deprecated <u> tag from account_sponsorship_page00:58
CIA-27Mantisbt: hickseydr * r9f6433e1c96f /core/bug_group_action_api.php: Issue #12545: Remove duplicate form closing tag (bug actiongroup)00:58
CIA-27Mantisbt: hickseydr * r90cc5cc12180 / (125 files in 6 dirs): Issue #12545: Remove deprecated <center> tag, align and valign attrs00:58
CIA-27Mantisbt: hickseydr * r246332d41d3c / (8 files in 3 dirs): Issue #12545: Remove deprecated <font> tags from XHTML output00:58
CIA-27Mantisbt: hickseydr * raa04132f79bd / (27 files in 5 dirs): Issue #12545: Remove deprecated border attribute00:58
CIA-27Mantisbt: hickseydr * r3045096dd7a0 / (3 files in 3 dirs): Issue #12545: Replace deprecated nowrap attribute with CSS equivalent00:59
CIA-27Mantisbt: hickseydr * r096b8c20314f /core/custom_function_api.php: Issue #12545: Replace deprecated <strike> tag with CSS equivalent00:59
CIA-27Mantisbt: hickseydr * r58f8ad2aeb22 /print_all_bug_page_word.php: Issue #12545: Remove deprecated clear attribute00:59
CIA-27Mantisbt: hickseydr * r6a0714fec042 / (5 files in 2 dirs): Issue #12545: Remove deprecated size and width attributes from <hr>00:59
*** Joins: Github (~Github@sh1-ext.rs.github.com)02:30
Githubmantisbt: master David Hicks * 7790835 (12 files in 6 dirs): Issue #12631: Replace old dynamic filter JavaScript code with jQuery ...02:30
Githubmantisbt: master David Hicks * cb5007d (1 files in 1 dirs): Issue #12545: Convert admin/check script to produce strict XHTML output ...02:30
Githubmantisbt: master David Hicks * e7ab342 (1 files in 1 dirs): Update jQuery UI to v1.8.702:30
Githubmantisbt: master David Hicks * 471900e (45 files in 6 dirs): Issue #12545: Replace &nbsp; with HTML5 compatible &#160; ...02:30
Githubmantisbt: master David Hicks * bac3bae (2 files in 1 dirs): Issue #12545: Replace last remaining <br>'s with <br /> ...02:30
Githubmantisbt: master David Hicks * 246332d (8 files in 3 dirs): Issue #12545: Remove deprecated <font> tags from XHTML output ...02:30
Githubmantisbt: master David Hicks * 49aac09 (54 files in 5 dirs): Issue #12545: Replace deprecated <b> tags with <strong> ...02:30
Githubmantisbt: master David Hicks * 6f0f593 (1 files in 1 dirs): Issue #12545: Remove deprecated <u> tag from account_sponsorship_page ...02:30
Githubmantisbt: master David Hicks * 9f6433e (1 files in 1 dirs): Issue #12545: Remove duplicate form closing tag (bug actiongroup) ...02:30
Githubmantisbt: master David Hicks * 90cc5cc (125 files in 6 dirs): Issue #12545: Remove deprecated <center> tag, align and valign attrs ...02:30
Githubmantisbt: master David Hicks * aa04132 (27 files in 5 dirs): Issue #12545: Remove deprecated border attribute ...02:30
Githubmantisbt: master David Hicks * 096b8c2 (1 files in 1 dirs): Issue #12545: Replace deprecated <strike> tag with CSS equivalent ...02:30
Githubmantisbt: master David Hicks * 58f8ad2 (1 files in 1 dirs): Issue #12545: Remove deprecated clear attribute ...02:30
Githubmantisbt: master David Hicks * 3045096 (3 files in 3 dirs): Issue #12545: Replace deprecated nowrap attribute with CSS equivalent ...02:30
*** Parts: Github (~Github@sh1-ext.rs.github.com)02:30
*** Quits: kirillka (~Miranda@156-237-55-95.baltnet.ru) (Quit: kirillka)02:57
*** Joins: paulr (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com)03:57
paulrMorning03:57
*** Joins: paulr_ (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com)04:06
*** Quits: paulr_ (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) (Quit: Friends help you move. Real friends help you move bodies.)04:06
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)04:10
*** Joins: giallu (~giallu@host118-186-dynamic.18-79-r.retail.telecomitalia.it)04:34
*** Quits: giallu (~giallu@host118-186-dynamic.18-79-r.retail.telecomitalia.it) (Changing host)04:34
*** Joins: giallu (~giallu@fedora/giallu)04:34
*** Joins: kirillka (~Miranda@201-226-55-95.baltnet.ru)04:48
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 276 seconds)05:10
*** Joins: giallu (~giallu@host244-189-dynamic.8-79-r.retail.telecomitalia.it)05:33
*** Quits: giallu (~giallu@host244-189-dynamic.8-79-r.retail.telecomitalia.it) (Changing host)05:33
*** Joins: giallu (~giallu@fedora/giallu)05:33
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)05:45
*** Joins: moto-moi (~hylke@2001:888:13e4:1010:21f:e2ff:fe0c:ce28)06:21
*** Joins: giallu (~giallu@host117-10-dynamic.9-79-r.retail.telecomitalia.it)07:00
*** Quits: giallu (~giallu@host117-10-dynamic.9-79-r.retail.telecomitalia.it) (Changing host)07:00
*** Joins: giallu (~giallu@fedora/giallu)07:00
paulrgiallu07:03
paulrwhat version of php does fedora ship nowadays?07:03
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 276 seconds)07:13
moto-moipaulr: core 6 seems to be shipping 5.1.6 ( http://archive.nl.eu.kernel.org/fedora-archive/core/6/x86_64/os/Fedora/RPMS/ )07:18
paulrhttp://distrowatch.com/table.php?distribution=redhat says 5.307:18
paulrdhx/myself talking about php versions07:18
moto-moimaybe they are looking at the development tree?07:22
paulrI thought 5.1.6 was rhel507:23
paulrhttp://www.redhat.com/rhel/server/details/07:27
paulrUpdates to the popular web scripting and programming languages PHP (5.3.2),07:28
CIA-27Mantisbt: hickseydr * r7a6fba7c7d89 /bugnote_add_inc.php: Issue #12545: Remove inline onclick attribute from bugnote submit button07:54
CIA-27Mantisbt: hickseydr * radf2338accb8 / (4 files in 4 dirs): Issue #12545: Remove inline JavaScript handlers from MantisGraph07:55
*** Joins: giallu (~giallu@host25-188-dynamic.32-79-r.retail.telecomitalia.it)08:38
*** Quits: giallu (~giallu@host25-188-dynamic.32-79-r.retail.telecomitalia.it) (Changing host)08:38
*** Joins: giallu (~giallu@fedora/giallu)08:38
giallupaulr, https://admin.fedoraproject.org/community/package_maintenance?package=php08:45
paulrso rhel = 5.3.2, MS = 5.2.14, fedore = 5.3.4, ubuntu = 5.308:50
paulrgiallu: trying to kill off adodb08:52
paulr:)08:52
giallupaulr, what's the plan?08:56
dhx1giallu: trying to move to using PDO08:57
dhx1giallu: paulr wants to have the option of writing alternative native SQL implementations of our database layer too08:57
dhx1giallu: although I disagree with that and would prefer to stick with PDO for everything (less code, less risk of bugs in a native implementation, etc)08:58
dhx1not that I mind too much either way at the moment... will wait and see what happens08:58
giallusigh08:59
dhx1giallu: regarding PHP versions I suggested we starting looking at using PHP 5.3 namespaces for some of the new code08:59
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)09:04
*** Joins: giallu (~giallu@fedora/giallu)09:08
gialluwhat strikes me is how I always start to work on stuff, then someone tells me paulr is in the same area09:11
gialluanyway, I'll just finish this stuff I'm on now, then push it somewhere and see09:12
CIA-27Mantisbt: hickseydr * r4b0e0d5d5494 / (4 files in 3 dirs): Issue #11826: Remove inline JavaScript for tag filter + date filter09:12
dhx1giallu: since when did you start? :)09:12
dhx1giallu: paulr started writing code just a few minutes ago, so it's not too late to collaborate (I'd encourage it)09:13
paulrdropping adodb has been on cards for a while09:13
paulrdhx/myself just took until last week to agree on pdo09:14
dhx1I always agreed on PDO btw :P09:14
*** Joins: thraxisp (~thraxisp@24.139.16.154)09:14
dhx1my aim here is to write the simplest database layer possible... and have it supported by someone else :P09:14
paulri'm just copying/pasting chunks of what I had before09:15
paulrheh09:15
dhx1(as long as it is still useful and functional)09:15
giallubtw. I helped a company to merge a couple servers they had with some new code I wanted to contribute, as it's basically a Zend based database layer09:15
gialluthe code I have now it's for 1.1, so I will need to adapt it to the 1.2 schema09:17
dhx1giallu: what does ZendDB add over native PDO?09:17
gialluno need to write SQL?09:18
dhx1my idea was to really just use PDO with some interception of calls to create a statement using a query string (so we can search/replace or translate queries between particulars of each database backend... ILIKE/LIKE, etc)09:18
dhx1abstractions of SQL are doomed IMO09:18
giallumy Django application for another project I'm working on does not agree... ;)09:19
dhx1they can't handle anything even remotely complex (SELECT COUNT(bugs.bug_id) AS count, users.reporter_name AS reporter FROM bugs LEFT JOIN users WHERE bugs.reporter_id = users.user_id ORDER BY users.reporter ASC)09:21
nuclear_eclipsejust as a point of interest, I've been using CodeIgniter's ActiveRecord in my latest project, and it has worked really well for everything except for compound where clauses, eg, if I want to do `where A and (B or C) and D`, I have to write that where clause myself09:21
nuclear_eclipsebut for everything else in the project, which is fairly complicated, it has been able to accomplish everything I've needed it to09:22
paulrwell, I was showing dhx a framework a while back where you have ->select()->where()->orderby() type thing abstraction09:22
nuclear_eclipsepaulr: that's basically what CI uses09:23
paulrbut david at least doesn't seem keen on having db_insert_record() type functions09:23
nuclear_eclipsehttp://codeigniter.com/user_guide/database/active_record.html09:23
dhx1it's also harder to read ->select()->where()->orderby().. than an SQL query09:23
dhx1and harder to debug and maintain (cannot trace a query from DB server logs to a location in the MantisBT source code as easily)09:24
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 276 seconds)09:25
paulrright now, i'm trying to get a 'simple' MantisDB layer09:26
paulrthat can replace adodb09:26
paulras we've been unable to "agree" on a db api (although that's more from random chats but)09:27
paulrStep 1: add MantisDB09:27
paulrStep 2: Bin adodb09:27
paulrStep 3: Add helper functions/hooks to do ->select or whatever09:27
paulrwe kinda know from looking at moodle/zend/ecz/symfony/<insert db framework here> that none meet out needs exactly09:27
paulrand for what we support it's probably quick enough to code our own09:28
*** Joins: giallu (~giallu@fedora/giallu)09:33
CIA-27Mantisbt: hickseydr * r2a1eed9db111 /core/http_api.php: Fix #11826: All inline JavaScript now removed09:34
gialluI'm on a flaky connection today :( anyway, after thinking about it a bit more, I don't see much overlap between my work and the "let's remove adodb" task09:34
dhx1Firefox 4 users rejoice! :)09:34
dhx1in the 1.3.x branch, Firefox 4 users are now protected against future XSS vulnerabilities... JavaScript code cannot be used in such attacks09:35
giallulet's party :)09:36
* giallu hates XSS09:36
dhx1next up on my security improvements list: output templating, mitigating timing attacks on logins, implementing RBAC to replace access_api, new authentication API09:38
paulrgiallu: dhx/myself had/have a bunch of stuff to push and some other stuff we want to get fixed09:38
thraxisppaulr: I don't understand why we need our own db abstraction? What is missing from moodle/zend/ecz/symfony/<insert db framework here>?09:38
* giallu loves thraxisp 09:38
paulrthraxisp: none of them handle the schema stuff09:39
thraxispI've not run across anything I can't do in Zend or Doctrine yet.09:39
paulror well, moodle's does09:39
thraxispSynphony / doctrine does09:39
paulrmoodle's was closest with there xmldb stuff, but it's hard to unbundle their layer09:39
dhx1why not just use PDO directly though... it's built into PHP, is least likely to become unmaintained, etc09:39
paulrthraxisp: not exactly :)09:39
paulrthraxisp: as they dont like ALTER statements in some cases09:39
paulre.g. where you've got existing date09:40
paulrer data09:40
paulrdhx wants to just use pdo directly09:40
paulrso we're probably more talking a simple wrapper09:40
paulrwe've hit issues with adodb where we've needed to patch it specifically for us09:41
paulrto the extent, trying to get those changes into upstream has wasted more time then i'd estimate our own layer would cost09:41
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)09:42
paulr( I need to replace adodb before 4th January when I go back to work, so I can upgrade mantis at work - as adodb = broken (as people dont want us adding our own patches)09:43
paulrAs of 6 weeks ago, the other frameworks still fail on some of our historical schema updates, or dont support all of the DB's we support etc09:44
paulr(technically we 'support' db2, oracle, pgsql, sqlsrv, mysql atm)09:44
dhx1paulr: by 4th January is a bit ambitious IMO09:44
dhx1paulr: the upgrade script will require a lot of thought09:45
paulrdhx1: did I mention i've got nothing else to do wiht my life until 4th? :)09:45
paulrcould be 30 hours of development :p09:45
dhx1:)09:46
paulralso, in terms of upgrade's09:46
dhx1just make sure you commit in small quantities09:47
paulri'd like to keep addob's datadict format09:47
dhx1as in, commit the backing classes09:47
dhx1then go through one file at a time updating the old DB code09:47
dhx1you'll notice HTML formatting in 1.3.x may be broken09:47
paulrhoping to keep db_query_bound at least as a compat layer09:47
dhx1and it won't work in IE < 9 at all... for now09:47
paulryea, i fixed a couple of issues in install.php09:48
dhx1I'm working to fix that ;)09:48
thraxispdhx1: Will it work in IE6 eventually? (40% of IE)09:48
dhx1thraxisp: not sure yet... I was thinking it'd be better to implement 2 "skins" - one very basic and supporting text browsers, IE6, etc - the other aimed towards modern browsers09:50
dhx1IE6 is dead anyhow09:50
dhx1when Google et al don't support it any more, I think it's safe to say that we don't need to either09:51
thraxispIt's 40% of the IE users. It's not dead yet.09:51
dhx1"support" = most features...09:51
thraxispMost are corporate  as well.09:51
dhx1I'm sure IE6 will render something, it just won't look good09:51
paulrthraxisp: I wouldn't worry too much about IE6, most of dhx's stuff doesn't work in chrome either :P09:52
thraxispSo we're going Win7 only :)09:52
paulrchrome trunk probably09:53
dhx1it's not possible to produce a skin aimed towards modern browsers that also works with IE609:53
dhx1there are too many things that break09:53
paulrdetect browser version in javascript :P09:54
thraxisphttp://code.google.com/p/ie7-js/09:54
dhx1that is why I was thinking of having a simple "text only" mode that is the simplest/dumbest interface possible09:54
dhx1almost "text only"09:54
dhx1with a minimal amount of CSS 2 thrown in09:55
paulrthraxisp: i'd say your numbers are out on ie6 btw09:55
paulr It's 40% of the IE users. It's not dead yet.09:56
paulr[02:51.25] <dhx1> "support" = most features...09:56
paulr[02:51.47] <thraxisp> Most are corporate  as well.09:56
paulr[02:51.47] <dhx1> I'm sure IE6 will render something, it just won't look good09:56
paulr[02:52.31] <paulr> thraxisp: I wouldn't worry too much about IE6, most of dhx's stuff doesn't work in chrome either :P09:56
paulr[02:52.58] <thraxisp> So we're going Win7 only :)09:56
paulr[02:53.21] <paulr> chrome trunk probably09:56
paulr[02:53.46] <dhx1> it's not possible to produce a skin aimed towards modern browsers that also works with IE609:56
paulr[02:53.54] <dhx1> there are too many things that break09:56
paulr[02:54.08] <paulr> detect browser version in javascript :P09:56
paulr[02:54.14] <09:56
paulrahh09:56
paulreww09:56
paulrhttp://stats.wikimedia.org/archive/squid_reports/2010-10/SquidReportClients.htm09:56
paulrwould imply more like 10% of ie users09:56
paulrhttp://www.w3counter.com/globalstats.php?year=2010&month=11 says 4.93% of web users on ie609:57
dhx1actually around 5% (considering mobile users aren't counted in the 5.32%)09:57
dhx1yep09:57
paulrhowever 5% of 200million is still quite a big number ;p09:57
paulrand dhx, I guess it's important to consider that mantis users might both be people/companies that either run cutting edge or old09:59
dhx1right - which is why I suggested two skins/frontends10:00
paulrhowever, IE6 is support by MS until end of support for XP10:01
paulrwhich is April 8th 201410:02
micahgI think most IE6 users are corporate users10:02
paulri'd be inclined to think by next summer most corporate users will be off IE6 or have plans in place10:03
paulri.e.10:03
paulrWin7 SP1 out, XP dying off - 2 year or whatever countdown10:03
paulrnew hardware etc10:03
dhx1well I think it'd be safe to make a MantisBT frontend that contains just the basic pages - view, edit, report, summarise, etc for IE6 users10:05
paulrif we release a mantis 1.3 in say... June July - 2-3 months after win7 SP1 - i'm not sure i'd necessarily see an issue with going "IE6 dropped, php5.3 only"10:05
dhx1and if anyone needs to manage their installation they can do so with a more modern browser10:05
paulrmore modern = google trunk?10:06
*** Joins: giallu (~giallu@fedora/giallu)10:06
dhx1paulr: I was thinking Firefox 3+10:06
paulrisn't 4 out?10:07
dhx1not yet10:07
paulrmaybe we should come up with some sort of policy on what we support ;)10:09
paulror more how we calculate what we support ;p10:09
dhx1we can support multiple things :)10:09
dhx1if we finally implement a theming/templating approach it'll be possible to have multiple versions of the same page10:09
paulrI was more thinking in terms of db's, php, browsers10:10
dhx1one version might use HTML5, another might use HTML4 with <font> tags... (I'm not helping with that :P)10:10
dhx1also worth noting is that IE6 users aren't going to install the latest MantisBT 1.3.x release10:10
dhx1they're going to opt for something "stable" like mantisbt-1.2.x10:11
dhx1Debian et al are still stuck with MantisBT 1.1.x!10:11
paulrdare I ask?10:12
micahgit's unfortunate, the upgrade scripts need updating and no one has had time yet10:19
paulrdare I ask10:20
paulrdoes that translate to10:20
paulrdebian doesn't want to / can't / won't use whatever mantis does, and haven't had time to upgrade their own scripts?10:20
dhx1paulr: they need maintainers to look after MantisBT, write the package script, etc10:21
paulrtar zxvf mnantisbt.tgz ; curl http://localhost/admin/upgrade.php10:23
micahgpaulr:: the debian package needs to update the db, it would be nice if we can get that to use the mantis upgrade mechanisms, but I haven't looked into the package policy enough to know if it's possible10:26
thraxispI talked with the debian maintainer about 3 years ago. Our upgrade script wasn't acceptable because it didn't use the debian way. I think that there is a bug in the tracker on this.10:28
* paulr sighs10:41
paulrwe'd be better asking them to drop the package fullstop then tbh ;p10:41
paulrhttp://people.debian.org/~seanius/policy/dbapp-policy.html/ch-dbapps.html10:43
paulr"while not essential, a set of common tools for packaging and configuring these applications can make the life of the maintainer as well as the administrator much easier."10:44
paulrso not essential?10:44
paulrso we can use our own10:44
paulrproviding it backs up first?10:44
*** Quits: paulr (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) (Read error: Connection reset by peer)10:48
*** Joins: paulr (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com)10:49
gialluumh. is it correct we now include/require files with the absolute paths?11:21
paulrno?11:27
paulror what do you mean11:27
paulrand yes, it would seem so11:29
paulrwe seem to include based on what library path and class path are set to11:29
gialluno way to disable it?11:29
paulrlooking, would seem not11:30
giallu:(11:30
paulror well, I guess it might fall through if files dont exist11:30
paulriirc, that was dhx :)11:30
gialluwell, I suspected "require_api" was going to bite me one day :)11:32
paulrheh11:32
paulrwell,11:32
paulr99% of people probably use tarball from site11:33
* paulr shrugs11:33
gialluonly if we believe Linux is under 1% ;)11:34
paulrwell it depends how many people use packages11:34
paulrbut yea11:34
paulrthe mess of what seems to be linux packaging is one of the reasons i'd rather write our own db layer11:35
giallupaulr, keyword is "seems"11:36
paulr:)11:36
paulrwell, the fact that ubuntu put on their LTS release (from April 2010) mantis 1.1, where we released 1.2.0 (february 2010), doesn't help to change my view :)11:37
gialluthat's not really a good example11:38
giallubut I see the point11:38
gialludistro needs do not always blend with upstream projects needs11:39
paulrmy issue is, if we add a library, in some cases, it causes more issues with the various distributions then not adding the library in the first place11:40
paulrwhich in some cases is a shame11:40
paulreven the license thing of our code11:41
paulrwe gotta jump through hoops to relicense it correctly11:41
gialluwell. that's not distro's fault11:42
paulrand I suspect that most people dont care :)11:42
paulryea11:42
paulrit doesn't help that mantis isn't really an entity11:43
gialluback to my issue. I'll need to investigate why we include stuff with absolute paths11:43
paulryou might find it falls through?11:43
paulri.e. if your in a plugin11:43
paulrtrying to include something11:43
paulryay12:00
*** Quits: giallu (~giallu@fedora/giallu) (Quit: Leaving)12:02
paulrnuclear_eclipse: can you do me a favour?12:16
nuclear_eclipsedepends12:23
*** Quits: thraxisp (~thraxisp@24.139.16.154) (Read error: Connection reset by peer)12:28
*** Joins: thraxisp (~thraxisp@24.139.16.154)12:28
*** Joins: Github (~Github@sh1-ext.rs.github.com)12:30
Githubmantisbt: master David Hicks * 7a6fba7 (1 files in 1 dirs): Issue #12545: Remove inline onclick attribute from bugnote submit button ...12:30
Githubmantisbt: master David Hicks * adf2338 (4 files in 4 dirs): Issue #12545: Remove inline JavaScript handlers from MantisGraph ...12:30
Githubmantisbt: master David Hicks * 4b0e0d5 (4 files in 3 dirs): Issue #11826: Remove inline JavaScript for tag filter + date filter ...12:30
Githubmantisbt: master David Hicks * 2a1eed9 (1 files in 1 dirs): Fix #11826: All inline JavaScript now removed ...12:30
Githubmantisbt: master commits 6a0714f...2a1eed9 - http://bit.ly/fyNdcS12:30
*** Parts: Github (~Github@sh1-ext.rs.github.com)12:30
paulrnuclear_eclipse: kill David for me :)12:46
nuclear_eclipseNot happening, he at least makes commits and doesn't complain about merging his working copy with latest master ;)12:46
paulrwe couldn't decide earlier12:47
paulrfor a user to upgrade to 1.312:47
paulrdoes he need to be able to do that from 1.0?12:47
nuclear_eclipseI would personally say yes, that's the entire point of us having versioned db schema from 1.0.012:49
paulrnodnod12:49
paulri'm just wondering about dates :P12:49
nuclear_eclipsewell, we could probably improve the migration process, but I definitely think it's important to maintain that upgrade path12:52
paulrI think i'm going to assume that db_query() is dead12:53
paulrnuclear_eclipse: what would you expect db_param() to insert into query?13:20
paulr:name or ? ?13:20
nuclear_eclipseI would expect it to be based on the database type in use, expecting it to send a proper parameterized query to the db13:21
paulrwith pdo? ;p13:21
paulrdhx seemed to think pdo'll handle it for us13:21
paulrI'm thinking therefore :1, :2 etc13:22
paulrso we can always replace :<int> with ?13:22
paulrbut we can define an order if needbe13:22
nuclear_eclipseI don't know anything about pdo, but my point is that I would expect it to be completely based on whatever our dbal says is the correct placeholder to use13:22
paulrPDO will emulate prepared statements/bound parameters for drivers that do not natively support them, and can also rewrite named or question mark style parameter markers to something more appropriate, if the driver supports one style but not the other.13:22
paulrThe SQL statement can contain zero or more named (:name) or question mark (?) parameter markers for which real values will be substituted when the statement is executed. You cannot use both named and question mark parameter markers within the same SQL statement; pick one or the other parameter style. Use these parameters to bind any user-input, do not include the user-input directly in the query.13:23
paulrYou must include a unique parameter marker for each value you wish to pass in to the statement when you call PDOStatement::execute(). You cannot use a named parameter marker of the same name twice in a prepared statement. You cannot bind multiple values to a single named parameter in, for example, the IN() clause of an SQL statement13:23
paulrso i'm basically thinking13:23
paulrwe should always use :name (as that allows us to alter order in php, and pdo magically deals with it13:23
nuclear_eclipsedoesn't matter to me as long as you support the existing usage of db_param and db_query_param -- I'll break your fingers if you break the way plugins are expecting to use the database api13:26
paulrdb_query = dead (but that's in database_api as 'will be removed before 1.2.0 final')13:49
paulri've got mysql working without adodb atm13:49
paulrand i've not actually written any code yet really13:49
paulr[06:26.09] <nuclear_eclipse> doesn't matter to me as long as you support the existing usage of db_param and db_query_param -- I'll break your fingers if you break the way plugins are expecting to use the database api13:56
paulrdb_query_param?13:56
paulryou meant bound?13:56
nuclear_eclipseyeah13:56
paulrdid we not add something so you could set order of db_param?13:57
nuclear_eclipseno13:57
paulrrephrase then13:57
paulrwould you like to be able to set order of db_param?13:57
paulri.e. if you could do either13:57
paulrbound( sql, array( 1,2,3) ;13:57
paulror13:57
paulrbound ( sql, array( 'p1'=>1, 'p3'=>3, 'p2'=>2);13:58
nuclear_eclipsemy point is that db_param() should default to being unordered imo, because there are places where db_param() isn't always called in the order it will appear in the query, although I could be wrong about that, but that assumption should IMO be maintained unless you add optional parameters to specify otherwise13:59
nuclear_eclipseunless that was always an incorrect assumption13:59
paulratm, we call db_param();14:00
paulras only way to call it14:00
paulrand for most part db_param is probably putting ? into query string14:00
paulrtherefore it's "ordered"14:00
nuclear_eclipseyes, I'm saying to maintain that as the default behavior14:01
paulrI thought we had some unordered stuff but i think I worked around that by building an array of params seperately to buidling the query14:01
* paulr grpes for db_param_count14:02
paulrbrilliant makes life easy14:03
paulrwhats actually going to be hardest is working out how/if we can translate the datetime<>int schema changes14:07
*** Joins: roentgen (~arthur@openvpn/community/support/roentgen)14:41
*** Quits: micahg (~micah@ubuntu/member/micahg) (Quit: Leaving.)16:03
*** Joins: micahg (~micah@ubuntu/member/micahg)16:04
dhx1paulr: use named parameters such as SELECT something FROM table WHERE field = :param;16:30
dhx1paulr: and then bind those parameters one per line as follows:16:30
dhx1$statement->bindParam(':param', $phpvar, PDO::PARAM_STR); etc16:31
dhx1unless you're referring to writing a compatibility layer with the old db_ API... in which case do whatever :)16:31
*** Quits: dhx1 (~anonymous@c122-107-170-247.eburwd5.vic.optusnet.com.au) (Remote host closed the connection)16:58
paulr:)17:11
paulrI guess that's dhx gone17:18
*** Joins: giallu (~giallu@fedora/giallu)17:42
*** Quits: roentgen (~arthur@openvpn/community/support/roentgen) (Ping timeout: 260 seconds)17:45
*** Joins: roentgen (~arthur@openvpn/community/support/roentgen)17:46
*** Quits: moto-moi (~hylke@2001:888:13e4:1010:21f:e2ff:fe0c:ce28) (Ping timeout: 260 seconds)17:47
gialluis admin/install.php borken on master?18:58
paulryes18:58
paulrI fixed it locally earlier18:59
paulror well, it's not broken but not rendering proper xhtml18:59
paulrso google chrome at least wouldn't display it18:59
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)19:00
paulrgiallu: can you do us a favour19:00
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)19:00
paulrdoes the current/"old" db debug stuff show the query BEFORE or AFTER parameters have been applied19:00
gialluFF3.6 not displaying it either19:03
paulrit does't return valid xhtml in trunk atm19:03
paulrI found this out when changing other stuff earlier ;/19:03
gialluyay for strict ;)19:03
giallupaulr, I'm not sure what you mean19:04
gialluwrt debug stuff19:04
paulri think i've worked it out19:07
paulrat one point we used to do the unique queries stuff19:07
paulrwas trying to remember what that built19:07
paulrgiallu: fedore has a mantis package?19:07
gialluyeah. 1.2 in what will be F15, 1.1 elsewhere19:08
paulrhow does it update the db?19:08
paulrvia our web scripts or?19:08
paulrgiallu: and yes 'strict' is starting to piss me off19:11
paulras it gives white pages :)19:11
gialluyeah, I'm wasting time there instead of doing the stuff I planned :(19:13
gialluso. I'm off to bed19:14
*** Quits: paulr (~IceChat09@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) (Quit: For Sale: Parachute. Only used once, never opened, small stain.)20:22

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!