On Thu, Nov 4, 2010 at 3:31 AM, tuxce <[email protected]> wrote: > Hi, I read that aur is in maintenance mode, but I try anyway: > https://bugs.archlinux.org/task/17583 > FS#17583 - JSON: enable multiple arguments for "info" method > > Patch also attached to bug report > > I tested it on current master git branch, it works. > > Thanks. >
I think this would be a nice feature and I would like to contribute. I attached a few patches to follow tuxce's. I noticed there is an old bug that reports an error in unicode if the string (before unicode conversion) is empty. Patch 1 fixes that. It would be useful if the results were ordered the same as the query arguments to make it easier for the RPC user to determine if the search failed and which result corresponds to which argument. If one of the provided arguments does not find a match in the DB than a null is returned in place of its result. Patch 2 does this. Patch 3 uses a regexp to make sure the argument used to search for an ID is strictly an integer and not a floating point or hexadecimal number. This doesn't really seem terribly important if a number with scientific notation or hexadecimal is sent in the DB SELECT but I thought it might be a good idea. -- -Justin
0001-Fix-misleading-bug-report-about-UTF8-for-an-empty-st.patch
Description: Binary data
0002-Force-info-RPC-to-order-results-the-same-as-argument.patch
Description: Binary data
0003-Use-regexp-to-accept-only-integers-for-the-ID-column.patch
Description: Binary data
