Mantis - ISSUES

0000016: Build errors

Sorry, not technically a crash but seemed to be the best available category.

I'm getting some build errors on Ubuntu Karmic (GCC 4:4.4.1-1ubuntu2 ) (UINT_MAX not defined, stdio and stlib errors)

Adding:

#include

to qot_ddl.h

and

#include
#include

to qot_app_args.cpp

Fixes them. Some Googling suggests GCC stopped including std libs by default around 3.4, don't know if it's the same issue, I'm not a C/C++ dev so it's all a bit outside my knowledge, found solutions from Google. ;)

After sorting those though I now get:

mv -f .deps/qot_app_args.Tpo .deps/qot_app_args.Po
make[3]: *** No rule to make target `qot_closure.o', needed by `qot'. Stop.
make[3]: Leaving directory `/home/tolan/ttmp/qot/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/tolan/ttmp/qot/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tolan/ttmp/qot'
make: *** [all] Error 2

I'm afraid I know nothing about Make, other than that I never want to ever have to know anything about it ;)

0000013: unambiguous columns are not recognized - "unresolved identifier"

Hi,

found another small glitch (on the other hand, it already proposed some indizes I wasn't able to find out...great :-) ).

If you specify a column that is unambiguous, MySQL will let you get away with it, but qot won't. Using your example tables "orders" and "clients" and running the following query
qot --input-file=schema.sql --input-query="SELECT * FROM clients c LEFT JOIN orders o ON o.client_id = c.id WHERE first_name = 'zaphod';" --info
results in the error message
ERROR 65000001 at 'first_name': unresolved identifier
though "first_name" could be resolved into a column of "clients".

Thanks again,
Philipp

0000015: BOOLEAN columns are not supported

If I extend the example table "orders" with a BOOLEAN column called "shipped" and execute the following query
qot --input-file=schema.sql --input-query="SELECT count(*) FROM orders WHERE shipped=0;" --info
I get a segmentation fault.

Changing the column's type to INT resolves the problem.

By the way: Might it be easier to read the database structure from the database directly instead of parsing the schema file? It seems to me that there's an awful lot that can go wrong when parsing this stuff...

Philipp

0000014: IFNULL produces segfault

...I've found another one - sorry ;-)

Running a statement containing MySQL's IFNULL function like
qot --input-file=schema.sql --input-query="SELECT IFNULL(amount,0) FROM orders WHERE id = 1;" --info
produces a segmentation fault.

Cheers,
Philipp

0000012: WHERE clauses on SMALLINT columns produce SEGFAULT

Hi,

first: Thanks for your work - this tools looks very promising!

Anyway, I just noticed that qot has a problem with queries against SMALLINT columns - modifying your example table to

CREATE TABLE clients (
id SMALLINT NOT NULL AUTO_INCREMENT PRIMARY KEY,
first_name VARCHAR(255),
last_name VARCHAR(255));

and executing
qot --input-file=schema.sql --input-query="SELECT * FROM clients WHERE id = 1;" --info

results in a "Segmentation fault".

Cheers,
Philipp

0000006: crash with bigint, datetime, enum field types

Under windows, it's crashing when the DDL has bigint, datetime and enum field types

0000011: Seg fault with LEFT OUTER JOIN queries

Any query containing LEFT OUTER JOIN gives a seg fault (the queries generated by rails active record uses "left outer join ").

If I remove the "OUTER" everything runs fine.

0000007: segmentation fault

just give a segmentation without any clue on what's happening by the way the version i'm using is 0.0.4.

0000008: Windows Binaries "The system cannot execute the specified program."

When trying to start qot.exe or qot-tests.exe,
get error saying "The system cannot execute the specified program."

Additionally, if trying to RegSvr32.exe any of the included .dlls,
get alert: "R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information."

0000004: Wishlist - more detail on error output, ability to control error output

This is against 0.0.3.

I have a large schema file which is basically a mysqldump without data. Once I add the CREATE DATABASE and USE statements, qot reads it in and uses it, but it prints out some errors:
error syntax error, unexpected IDENT_QUOTED, expecting ')' met

1. I would like to request that the syntax error output also print the line number (if that info is available, if it's just in a struct and parsed char-by-char, then probably not and it's not worth keeping track of that info).

2. I would like to request a -q option to quiet error output or wrap it with /* */.

0000003: Segfault for queries that use table alias

This is for 0.0.3 which is not yet able to be chosen in Product Version field.

This query type works:
SELECT table.field FROM table WHERE table.field2 = 'x';

These query types segfault:
SELECT t1.field FROM table AS t1 WHERE t1.field2 = 'x';
SELECT t1.field FROM table t1 WHERE t1.field2 = 'x';

0000005: Various segfaults

$ qot --input-file=test.sql --input-query='SELECT channel FROM test where id=5' --info
/* Output produced by qot 0.0.3 GPL */
/*
... all good
*/

$ qot --input-file=test.sql --input-query='SELECT channel FROM test2 where id=5' --info
Segmentation fault

$ qot --input-file=test.sql --input-query='SELECT channel, count(*) FROM test group by channel' --info
Segmentation fault

I really love the idea and I would love to start using qot, but the program so far is missing absolutely basic checks and segfaults with no indication of what's wrong. Granted, the first query tries to use a table that doesn't exist, but the 2nd one uses a perfectly valid count(*), which seems to be the culprit here.

0000002: Segfault if query-file doesn't start with create database and use commands

This is for 0.0.3, it's not yet able to be chosen in the Product Version field.

It seems silly that a user wouldn't understand that it's a required part of the sql file, but to make qot more resilient it should gracefully handle the absence of those required parts. qot should do one of two things:
- spit out an error if it encounters a CREATE TABLE before a CREATE DATABASE/SCHEMA and a USE statement
- or silently assume a 'CREATE DATABASE test;' and 'USE test;'.

0000001: Compilation fails

$ ./configure --prefix=/usr
$ make
...
gcc -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT strxmov.o -MD -MP -MF .deps/strxmov.Tpo -c -o strxmov.o strxmov.c
mv -f .deps/strxmov.Tpo .deps/strxmov.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT xml.o -MD -MP -MF .deps/xml.Tpo -c -o xml.o xml.c
mv -f .deps/xml.Tpo .deps/xml.Po
rm -f libsqlparser-noinst.a
ar cru libsqlparser-noinst.a charset-def.o charset.o ctype-big5.o ctype-bin.o ctype-cp932.o ctype-czech.o ctype-euc_kr.o ctype-eucjpms.o ctype-extra.o ctype-gb2312.o ctype-gbk.o ctype-latin1.o ctype-mb.o ctype-simple.o ctype-sjis.o ctype-tis620.o ctype-uca.o ctype-ucs2.o ctype-ujis.o ctype-utf8.o ctype-win1250ch.o ctype.o dllmain.o int2str.o my_lib.o my_messnc.o my_static.o my_strtoll10.o my_vsnprintf.o myx_lex_helpers.o myx_sql_parser.tab.o myx_sql_tree_item.o myx_statement_parser.o myx_unicode_scanner.o str_alloc.o strmake.o strnmov.o strtod.o strxmov.o xml.o
ranlib libsqlparser-noinst.a
make[3]: Leaving directory `/home/bla/mysql/qot/src/sql-parser'
make[3]: Entering directory `/home/bla/mysql/qot/src'
g++ -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -MT qot.o -MD -MP -MF .deps/qot.Tpo -c -o qot.o qot.cpp
In file included from qot_select_query.h:26,
from qot.cpp:28:
qot_expression.h:514: error: base `qot::expr::Expr' with only non-default
constructor in class without a constructor
qot_expression.h:838: error: base `qot::join::Table_ref' with only non-default
constructor in class without a constructor
make[3]: *** [qot.o] Error 1
make[3]: Leaving directory `/home/bla/mysql/qot/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/bla/mysql/qot/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bla/mysql/qot'
make: *** [all] Error 2