Drizzle client hash completion generates SQL errors

Bug #677013 reported by Andrew Hutchings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Andrew Hutchings
7.0
Fix Released
Medium
Andrew Hutchings

Bug Description

Whilst breaking on "my_printf_error" I accidentally found that the drizzle client's hash completion generator routine is getting SQL errors on:

show fields in 't2'

But silently hiding them.

Backtrace on Drizzle server side:

#0 drizzled::my_printf_error (error=1064,
    format=0xd1aba8 "%s near '%-.80s' at line %d", MyFlags=0)
    at drizzled/error.cc:152
#1 0x000000000068c1da in DRIZZLEparse (yysession=0x1840c10)
    at drizzled/sql_yacc.cc:17758
#2 0x000000000066b3fc in parse_sql (session=0x1840c10,
    inBuf=0x184b028 "show fields in 't2'", length=19)
    at drizzled/sql_parse.cc:1773
#3 drizzled::mysql_parse (session=0x1840c10,
    inBuf=0x184b028 "show fields in 't2'", length=19)
    at drizzled/sql_parse.cc:738
#4 0x000000000066d8aa in drizzled::dispatch_command (
    command=<value optimised out>, session=0x1840c10,
    packet=0x183cc01 "show fields in 't2'",
    packet_length=<value optimised out>) at drizzled/sql_parse.cc:228
#5 0x0000000000645b2a in drizzled::Session::executeStatement (this=0x1840c10)
    at drizzled/session.cc:704
#6 0x000000000064b35f in drizzled::Session::run (this=0x1840c10)
    at drizzled/session.cc:547
#7 0x00007ffff18aa94b in MultiThreadScheduler::runSession (this=0x181c660,
    session=0x1840c10) at plugin/multi_thread/multi_thread.cc:50
#8 0x00007ffff6b698e0 in thread_proxy ()
   from /usr/lib/libboost_thread.so.1.44.0
#9 0x00007ffff543d971 in start_thread (arg=<value optimised out>)
    at pthread_create.c:304
#10 0x00007ffff519994d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Related branches

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.