Bug #15359 | inet_ntoa output truncated when data is grouped | ||
---|---|---|---|
Submitted: | 30 Nov 2005 17:27 | Modified: | 2 Jan 2006 7:50 |
Reporter: | Rob Walters | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.1.17 | OS: | Windows (Windows XP Pro, SP2) |
Assigned to: | CPU Architecture: | Any |
[30 Nov 2005 17:27]
Rob Walters
[1 Dec 2005 7:47]
Valeriy Kravchuk
Thank you for a problem report. What version of MySQL server do you use? I was not able to repeat the problem you described on 5.0.15-nt. I performed the following steps: mysql> create table iphdr(c1 int auto_increment primary key, ip_src int); Query OK, 0 rows affected (0.10 sec) mysql> insert into iphdr(ip_src) values (1044005859); Query OK, 1 row affected (0.02 sec) mysql> insert into iphdr(ip_src) values (1044005859); Query OK, 1 row affected (0.09 sec) mysql> insert into iphdr(ip_src) values (1090445564); Query OK, 1 row affected (0.03 sec) mysql> select * from iphdr; +----+------------+ | c1 | ip_src | +----+------------+ | 1 | 1044005859 | | 2 | 1044005859 | | 3 | 1090445564 | +----+------------+ 3 rows in set (0.02 sec) mysql> select ip_src,inet_ntoa(ip_src) from iphdr group by ip_src; +------------+-------------------+ | ip_src | inet_ntoa(ip_src) | +------------+-------------------+ | 1044005859 | 62.58.67.227 | | 1090445564 | 64.254.224.252 | +------------+-------------------+ 2 rows in set (0.03 sec) mysql> select version(); +-----------+ | version() | +-----------+ | 5.0.15-nt | +-----------+ 1 row in set (0.01 sec) That query, select ip_src,inet_ntoa(ip_src) from iphdr group by ip_src, gave me exactly the same result in Query Browser 1.1.17 on plain XP. I can post a screenshot, if you want. So, please, check once more and describe the steps I have to perfrom to see the problem you described.
[2 Dec 2005 7:50]
Valeriy Kravchuk
Thank you for the additional test. Yes, your 4.1.8a is really old. It may contain bugs, that are already solved. So, please, upgrade to 4.1.15 (or wait for the 4.1.16 to come soon) and try to repeat the same steps. Inform about the results.
[3 Jan 2006 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".