Re: [aur-dev] AurJson - orphan packages

2009-09-17 Thread Gergely Imreh
2009/9/17 Loui Chang louipc@gmail.com: On Thu 17 Sep 2009 12:31 +0800, Gergely Imreh wrote: Also, I'm a bit puzzled by the objection to a single line of $row['Orphan'] = ($row['MaintainerUID'] == 0 ? 1 : 0); which was countered with a suggestion of a full database re-query. Would THAT

Re: [aur-dev] AurJson - orphan packages

2009-09-16 Thread Loui Chang
On Thu 17 Sep 2009 10:34 +0800, Gergely Imreh wrote: 2009/9/17 Loui Chang louipc@gmail.com: On Mon 14 Sep 2009 22:46 +0800, Gergely Imreh wrote: The following patch adds the Orphan field to the aurjson output. For username we would need  to hit the database once more (maybe, have to

Re: [aur-dev] AurJson - orphan packages

2009-09-16 Thread Dan McGee
On Wed, Sep 16, 2009 at 10:43 PM, Loui Chang louipc@gmail.com wrote: On Thu 17 Sep 2009 10:34 +0800, Gergely Imreh wrote: 2009/9/17 Loui Chang louipc@gmail.com: On Mon 14 Sep 2009 22:46 +0800, Gergely Imreh wrote: The following patch adds the Orphan field to the aurjson output. For

Re: [aur-dev] AurJson - orphan packages

2009-09-16 Thread Dan McGee
On Wed, Sep 16, 2009 at 11:31 PM, Gergely Imreh imr...@gmail.com wrote: Having said all this, I can see the point of returning the username / orphan (or username / ?) instead of Orphan logical variable. I wouldn't have chosen it myself originally because of the extra database hit, but now it

Re: [aur-dev] AurJson - orphan packages

2009-09-16 Thread Gergely Imreh
2009/9/17 Dan McGee dpmc...@gmail.com: On Wed, Sep 16, 2009 at 11:31 PM, Gergely Imreh imr...@gmail.com wrote: Having said all this, I can see the point of returning the username / orphan (or username / ?) instead of Orphan logical variable. I wouldn't have chosen it myself originally because

Re: [aur-dev] AurJson - orphan packages

2009-09-16 Thread Loui Chang
On Thu 17 Sep 2009 12:31 +0800, Gergely Imreh wrote: Also, I'm a bit puzzled by the objection to a single line of $row['Orphan'] = ($row['MaintainerUID'] == 0 ? 1 : 0); which was countered with a suggestion of a full database re-query. Would THAT really take that much shorter? Have to do some