Compilation failure on SLES11SP1 with gcc 4.3.4

Kristofer Wempa — Thu, 12 Jan 2012 16:13:14 -0000

I had no problems compiling on SLES10. However, I ran into the following compilation error on SLES11SP1 using gcc 4.3.4:

shsqlinp.c:49: error: conflicting types for getline
/usr/include/stdio.h:653: error: previous declaration of getline was here
shsqlinp.c:374: error: conflicting types for getline
/usr/include/stdio.h:653: error: previous declaration of getline was here

There is apparently a conflict with an existing symbol in stdio.h. I solved the issue by changing all 3 instances of the string "getline" to "get_line" within shsqlinp.c.

shsql returns values when should be null

Joel Fouse — Tue, 21 Mar 2006 00:14:17 -0000

Given the following test setup:

create table shtest (
a int,
b int
);
insert into shtest values (0, null);
insert into shtest values (1, 1);
insert into shtest values (2, null);
insert into shtest values (3, null);
insert into shtest values (4, 4);
insert into shtest values (5, null);

The command:

shsql $HANDLE "select * from shtest";

...returns the following:

"0" ""
"1" "1"
"2" "1"
"3" "1"
"4" "4"
"5" "4"

So what's happening is that when it encounters a null
in the second column AFTER having previously returned a
value in that column, it's simply returning the value
it had for that column in the previous row for EVERY
row until it has a new value. More to the point, some
value isn't getting zeroed out in the loop.

I'm currently using ms-sql, so connecting through
freetds. I have not yet had an opportunity to test
against other data sources. Nor do I have the time
now, though I'm curious to try, to work through
debugging this. If I manage, I will submit a patch,
but I'm not sure how soon I'll be able to do that.

Recent changes to bugs

Compilation failure on SLES11SP1 with gcc 4.3.4

shsql returns values when should be null