Bingjie Miao on the optimizer team tells me this bug was indeed fixed
already. He already sent a reply posting via a moderated feed, so it
should
arrive here eventually. :-)
--
Kevin Cherkauer
Software Engineer
IBM Informix Dynamic Server -- Database Kernel
"Kevin Cherkauer" <invalid_address@[EMAIL PROTECTED]
> wrote in message
news:fvt3g8$c9o$1@[EMAIL PROTECTED]
>I just tried this on recent builds of the next-to-be-released 10.00,
11.10,
>and 11.50 versions (currently these are numbered 10.00.xC9, 11.10.xC2W3,
>11.50.xC2; of course these numbers might change and my posting this is no
>guarantee from IBM that these will necessarily be released...), and it
>worked correctly on all of them. All of these were on 64-bit x86 Linux.
The
>same query also worked against a regular table on all of them. (sysmaster
>tables are not normal tables -- they are what we call pseudotables. The
>code to access them produces them out of thin air, or rather out of the
>contents of memory on the fly, so it's possible for some things to be
>broken for particular sysmaster tables that work correctly for other
>sysmaster tables and normal tables.)
>
> This has the flavor of a bug that has already been found and fixed in
> later fixpacks. I will ask the optimizer team if they know of any such
fix
> having been done.
>
> --
> Kevin Cherkauer
> Software Engineer
> IBM Informix Dynamic Server -- Database Kernel
>
>
> "piotrek" <piotrUSUN_T_O110@[EMAIL PROTECTED]
> wrote in message
> news:fvsfda$4q7$1@[EMAIL PROTECTED]
>> IBM Informix Dynamic Server Version 10.00.UC5 on redhat
>>
>> Try this:
>> SELECT MIN(colno) FROM syscolumns WHERE colno>=1 AND colno>1
>> An the answer is ..... 1
>> A know that stupid questions generates stupid answers but still....
>>
>> Anyone has come to that?
>
>
|
