Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Mike Keen <mk@visiture.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Tue, 11 May 2010 15:36:55 -0400
Subject: Re: Strange integer anomaly in Erlang view
Thread-Topic: Strange integer anomaly in Erlang view
Thread-Index: AcrxQVFgyqaGCBdDQcyOppV/wSFfyw==
Message-ID: <126D1B3E-8E6D-4AC9-B126-0C90E23307EE@visiture.com>
References: <F9C46553-552A-45F6-82CA-45114193E48C@visiture.com>
 <AANLkTin66LAcQY4AQGWNEHYnwOISZMKdrPpPoCJdzxST@mail.gmail.com>
 <AANLkTinvCullabBtesCfps6PJ3ZiTfOhFm9HI31X-O-2@mail.gmail.com>
 <0B8367C6-CECE-48FB-AE62-1C270DE70221@visiture.com>
 <AANLkTimBUtZjbXyQ9ObdYyajLUK0Qd7DnKtkTAVS-ytw@mail.gmail.com>
 <C0DFBFB4-1CD0-4C4C-97A9-43AF9B12B242@visiture.com>
 <AANLkTilW_93Xf7i_0u5LCs6heABEd5jZn_i6h2UdCtTK@mail.gmail.com>
 <AANLkTimr82P73tRNrpMhVe58Ftg5rTqtlGkrSNf7xmcJ@mail.gmail.com>
 <B22E9187-F51B-46FA-9FD1-EC611ABF76B7@visiture.com>
 <059B0C98-2D2F-4F09-A867-4D6ABFB1C335@apache.org>
In-Reply-To: <059B0C98-2D2F-4F09-A867-4D6ABFB1C335@apache.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Adam,

That's the problem. I feel a little stupid, but I appreciate the nudge in t=
he right direction!

Mike

On May 11, 2010, at 3:23 PM, Adam Kocoloski wrote:

> Hi Mike, are you sure this is what you want?
>=20
>>     [Emit(proplists:get_value(<<"id">>, StrippedCampaign, null), Campaig=
n) || Campaign <- AdwordsCampaigns, {StrippedCampaign} <- AdwordsCampaigns]=
;
>=20
> Try it in the emulator
>=20
> 1> Foo =3D [1,2,3].
> [1,2,3]
> 2> [{X,Y} || Y <- Foo, X <- Foo].
> [{1,1},{2,1},{3,1},{1,2},{2,2},{3,2},{1,3},{2,3},{3,3}]
>=20
> You're generating combinatoric pairs of all elements of AdwordsCampaigns,=
 pulling the key from the first element of the pair and the value from the =
second part of the pair.  Perhaps you're looking for this instead?
>=20
> [Emit(proplists:get_value(<<"id">>, Campaign, null), {Campaign}) || Campa=
ign <- AdwordsCampaigns];
>=20
> Best, Adam
>=20
> On May 11, 2010, at 2:58 PM, Mike Keen wrote:
>=20
>> You're right. In the value column, the id shows up as 50573744 which is =
the correct value. In the key column, it shows up as 53518364.
>>=20
>> On May 11, 2010, at 2:44 PM, Randall Leeds wrote:
>>=20
>>> On Tue, May 11, 2010 at 11:40, Jarrod Roberson <jarrod@vertigrated.com>=
 wrote:
>>>> On Tue, May 11, 2010 at 2:31 PM, Mike Keen <mk@visiture.com> wrote:
>>>>=20
>>>>> I guess I'm confused as to why JavaScript is ever even involved when
>>>>> writing views in Erlang. Excuse my ignorance, but does all JSON go th=
rough
>>>>> it?
>>>>>=20
>>>>> Mike
>>>>>=20
>>>>> read all the comments to that bug report, it is the JSON parser that
>>>> conforms to the limitations of JavaScript. And everything goes thru th=
e JSON
>>>> parser.
>>>>=20
>>>=20
>>> I think we're missing the point. Even if the erlang JSON parser
>>> conforms to JSON's notion of numbers then I'd expect the id to be
>>> transformed the same way for both the key and the value.
>>>=20
>>> Maybe the key is implicitly treated as a string? Mike, which is the
>>> "correct" value for the id?
>>=20
>=20