ty. good idea.
On Jul 20, 6:52 pm, JDG wrote:
> the twitpocalypse happened quite a few weeks ago and this was discussed ad
> nauseum. If json_decode is trying to put those into an int instead of a 64
> bit number (a la long long or BigInteger in java), you should probably
> modify the json text,
the twitpocalypse happened quite a few weeks ago and this was discussed ad
nauseum. If json_decode is trying to put those into an int instead of a 64
bit number (a la long long or BigInteger in java), you should probably
modify the json text, adding quotes, before you call json_decode, so that it
i
i guess it works on my machine because my machine is 64 bit and recent
status ids are up 2 billion and 700 million
On Jul 20, 6:42 pm, dexxa wrote:
> well. the id of said problem is 2147483647 which is the largest signed
> positive integer. so status id is too big and being intepretted as
> inte
well. the id of said problem is 2147483647 which is the largest signed
positive integer. so status id is too big and being intepretted as
integer instead of string?? so its overflowing
anyone? any idea?
On Jul 20, 6:33 pm, dexxa wrote:
> well i upgraded my local machine to php 5.3 and strang
well i upgraded my local machine to php 5.3 and strangely it works
fine. so only linux version of php 5.3 has problem? this is weird.
anyone know why?
On Jul 20, 5:54 pm, dexxa wrote:
> hmm turned out to be json_decode problem. and the strange thing is
> that the problem is caused by php 5.3. an
hmm turned out to be json_decode problem. and the strange thing is
that the problem is caused by php 5.3. and it runs fine on my local
machine which has php 5.2.1
On Jul 20, 5:11 pm, dexxa wrote:
> hello, very strange i am getting same status/tweet id for all of my
> search api results.
>
> my r
