Re: monetdb lost column info when queryring

8 Aug 2013

      Hi Martin,
The last mail i sent just is a show of some bug in MonetDB,
It demonstrated a realistic application of MonetDB in Internet Industry, which is the first time MonetDB applied in the Top 3 internet company ,a valuable example MonetDB applied to.

I just want to help improve MonetDB by fixing some little and serious bug , this is out of my passion for it.

Regards,
Meng
------------------ Original ------------------
From:  "Martin Kersten";
Date:  Thu, Aug 8, 2013 03:38 PM
To:  "users-list"; 

Subject:  Re: monetdb lost column info when queryring

                   Dear Meng,

       Could you please keep this mail channel free from very application       specific issues!!!
       It reaches many that don't have a clue about your application       setting, nor the time
       to help you in this. For them this turns into spam.

       I urge you to scout locally for a database expert to help you       debug your software.
       In case of a potential bug, we are more then welcome to study the       minimal, fully
       documented and repeatable setup.

       Furthermore, the mail list archive is a good source for additional       information about
       phenomenons observed.

       regards, Martin

       On 08/08/2013 09:21 AM, integrity wrote:

                     sql>select * from kbms_logserver_msg t             where  command = 'CmdWxInfo' and logdate = '2013-08-06' and             functionret <> '0' and servertime > '1375757230'             limit 10; 
 +------------+-----------+--------------+-------------+----------+------------+---------------+------------+----------------+------------+------------+
             | logdate    | command   | commandtype  | functionret |             costtime | servertime | serverip      | serverport |             clientip       | clientport | clienttype |
 +============+===========+==============+=============+==========+============+===============+============+================+============+============+
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3032 | 1375757231 | 10.187.143.80 | 7000       |             10.153.130.228 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3032 | 1375757244 | 10.187.143.80 | 7000       |             10.153.130.228 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3030 | 1375757257 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3032 | 1375757962 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3030 | 1375757970 | 10.187.143.80 | 7000       |             10.153.130.228 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535             |       60 | 1375760693 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535             |       60 | 1375760693 | 10.187.143.80 | 7000       |             10.153.130.228 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535             |       59 | 1375760693 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535             |       63 | 1375760872 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535             |       54 | 1375760872 | 10.187.143.80 | 7000       |             10.153.130.229 |            |            |
 +------------+-----------+--------------+-------------+----------+------------+---------------+------------+----------------+------------+------------+
             10 tuples (55.709ms)

             sql>select * from kbms_logserver_msg t where  command =             'CmdWxInfo' and logdate = '2013-08-06' and functionret             <> '0' and servertime = '1375757231' limit 10; 
 +------------+-----------+--------------+-------------+----------+------------+---------------+------------+----------------+------------+------------+
             | logdate    | command   | commandtype  | functionret |             costtime | servertime | serverip      | serverport |             clientip       | clientport | clienttype |
 +============+===========+==============+=============+==========+============+===============+============+================+============+============+
             | 2013-08-06 | CmdWxInfo | getwxinfoall |        -535 |                 3032 | 1375757231 | 10.187.143.80 | 7000       |             10.153.130.228 | 44328      |            |
 +------------+-----------+--------------+-------------+----------+------------+---------------+------------+----------------+------------+------------+
             1 tuple (52.761ms)
         in the first query,when servertime > '1375757230' limit           10;clientport are all NULL.
         while in             the second query, servertime = '1375757231' ,clientport             appeard again.
         it proves that the clientport exist but just didn't appear           in the query.

         Thanks,

       Meng

       _______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list