Re: BUG on 64bit & if a value is quoted (4.0.17 / 4.1.2 / 5.0.0)

2004-02-01 Thread Stefan Traby
On Sat, Jan 31, 2004 at 10:06:04PM -0500, Michael Stassen wrote: > Meanwhile, perhaps a simpler workaround would be to change how you build > the query in Perl so as to avoid the quotes. Well, I know that this would be easy but I have good reasons to avoid this. The most important one is lru sta

Re: BUG on 64bit & if a value is quoted (4.0.17 / 4.1.2 / 5.0.0)

2004-01-31 Thread pcg
On Sat, Jan 31, 2004 at 10:06:04PM -0500, Michael Stassen <[EMAIL PROTECTED]> wrote: > Meanwhile, perhaps a simpler workaround would be to change how you build > the query in Perl so as to avoid the quotes. Unfortunately, the heuristic that DBD::mysql uses cannot be changed or forced. Currently,

Re: BUG on 64bit & if a value is quoted (4.0.17 / 4.1.2 / 5.0.0)

2004-01-31 Thread Michael Stassen
I think the problem has nothing to do with &. Taking the & out of your examples leaves you with: mysql> select '9223372036854775809' + 0; +---+ | '9223372036854775809' + 0 | +---+ | 9.2233720368548e+18 | +---+ mysql> s

Re: BUG on 64bit & if a value is quoted (4.0.17 / 4.1.2 / 5.0.0)

2004-01-31 Thread Stefan Traby
WOW !! The story goes on: I wrote the UDF-Functions (and64/or64) and while and it seems to work: mysql> select and64('9223372036854775809',127); +--+ | and64('9223372036854775809',127) | +--+ |1 | +--

BUG on 64bit & if a value is quoted (4.0.17 / 4.1.2 / 5.0.0)

2004-01-31 Thread Stefan Traby
Hi ! select 129 & 127; -- ok(1) select '129' & 127; -- ok(1) select (0+'129') & 127; -- ok(1) select CAST('129' AS UNSIGNED INTEGER) & 127; -- ok(1) select CONVERT('129', UNSIGNED INTEGER) & 127;-- ok(1) Doing the same wi