Wow! I have been waiting it since HipHop was released. Great job! Thanks. 2010/9/22 <development-request@drupal.org>:
Send development mailing list submissions to development@drupal.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/mailman/listinfo/development or, via email, send a message with subject or body 'help' to development-request@drupal.org
You can reach the person managing the list at development-owner@drupal.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of development digest..."
Today's Topics:
1. Drupal.org on HipHop (Gerhard Killesreiter) 2. Re: Problem with db_affected_rows() in MySQL (Nikola Kotur) 3. Re: Problem with db_affected_rows() in MySQL (Bob Hutchinson) 4. Re: Drupal.org on HipHop (Gerhard Killesreiter) 5. Re: Drupal.org on HipHop (Dipen)
----------------------------------------------------------------------
Message: 1 Date: Wed, 22 Sep 2010 12:49:53 +0200 From: Gerhard Killesreiter <gerhard@killesreiter.de> Subject: [development] Drupal.org on HipHop To: "Drupal.org Infrastructure Maintainers" <infrastructure@drupal.org>, development@drupal.org Message-ID: <4C99DF51.1070009@killesreiter.de> Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi there,
I've been following the development of Facebook's HipHop PHP compiler since February with the intention of setting up a copy of drupal.org on it. This has now been achieved, see http://driphop.drupal.org/
This runs on a copy of the database, so feel free to make any changes. It uses bakery for authentication, so you should be able to log-in.
Please report any errors you notice in the infrastructure issue queue, I've added a driphop.drupal.org component.
The website might be unavailable from time to time.
I have not yet done any proper benchmarks for this setup. The aim here is to find bugs (the fastest php page is the one with a parse error after all...).
Known bugs:
1) Due do some issue with the way URL rewriting works in Hiphop vs how t works in apache, the homepage gives you a 404 but does actually show the orange d.o box. /node does work, but does not show you the orange box...
2) The local task tabs lack some HTML that the CSS needs to render them properly. Somehow the relevant theme function doesn't appear to get called.
3) I've had to remove three blocks that use PHP in the "pages" column.
4) Uploaded files are not available and none can be uploaded.
Thanks to Narayan for getting me a database and to the OSL for loaning us another VM.
Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkyZ31EACgkQfg6TFvELooTKLACfUZn2xwluH1u7DChZEtyvo6DG HYoAoLuCR8PD/5ypWbeUkrs4Yeb6NXhO =DetO -----END PGP SIGNATURE-----
------------------------------
Message: 2 Date: Wed, 22 Sep 2010 12:51:17 +0200 From: Nikola Kotur <kotnick@gmail.com> Subject: Re: [development] Problem with db_affected_rows() in MySQL To: development@drupal.org Message-ID: <1285152677.3556.15.camel@eton> Content-Type: text/plain; charset="utf-8"
On Wed, 2010-09-22 at 15:05 +0530, sivaji j.g wrote:
I assume this is with an intention of avoiding duplicate records inserts. However in my case db_affected_rows() mostly returns 0 though a matching row is found in the table.
I guess it is because the values being updated is same as values already available in the row.
Yes, as MySQL documentation clearly states:
For UPDATE statements, the affected-rows value by default is the number of rows actually changed. If you specify the CLIENT_FOUND_ROWS flag to mysql_real_connect() when connecting to mysqld, the affected-rows value is the number of rows ?found?; that is, matched by the WHERE clause.
http://dev.mysql.com/doc/refman/5.1/en/mysql-affected-rows.html