[Discuss] mysql mystery

[Stephen Adler]

Thanks Mark, It turned out to be something totally different. I exited 
firefox and started it up again and it worked fine. I then made sure I 
executed mysql_close() each time I opened a connection to the server. 
I've got my fingers crossed I fixed the problem.

Thanks!

On 08/20/2011 05:05 PM, Mark Woodward wrote:
> I strongly suspect the query. Are you doing an outer join or anything 
> like that? One of the problems of doubles is that even equal seeming 
> numbers are seldom equal.  For instance, this clause "WHERE col = 1" 
> would work for an integer, but only works for some values of "1" 
> depending on precision and rounding. This is why doubles are evil. 
> They are OK for calculations and relative compares, i.e. < or >, but 
> "=" is bad.
>
>
> On 08/20/2011 01:36 PM, Stephen Adler wrote:
>> The mystery deepens... I converted the column of type double to a 
>> type varchar(16) and I still get a null result when I query the 
>> column... uggg...
>>
>> On 08/20/2011 12:56 PM, Stephen Adler wrote:
>>> Hi All,
>>>
>>> I've run into a problem with mysql/php. I have a table in which one 
>>> of the columns is defined as a double. The problem is that when I 
>>> fetch the contents of that column from my php script, the value gets 
>>> nulled out. Doing a sql query from the command line mysql tool 
>>> returns a non null decimal number, but that same query returns a 
>>> nulled value in php. The columns defined as integers works fine and 
>>> of course the string type columns work fine as well. Any ideas?
>>>
>>> thanks. Steve.
>>>
>>> _______________________________________________
>>> Discuss mailing list
>>> Discuss at blu.org
>>> http://lists.blu.org/mailman/listinfo/discuss
>>>
>>
>> _______________________________________________
>> Discuss mailing list
>> Discuss at blu.org
>> http://lists.blu.org/mailman/listinfo/discuss
>