invalid tuple received from server, got 17 columns, expected 24, ignoring #2963
Last updated: 2012-01-26 15:32:02 +0100
Date: 2012-01-04 09:27:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux ppc; rv:5.0) Gecko/20100101 Firefox/5.0
note: to disable dropping columns and/or truncating fields use \w-1
Steps to Reproduce:
MonetDB 5 server v11.8.0 (64-bit, 64-bit oids)
Date: 2012-01-04 09:47:26 +0100
What is the contents of columns 17 and 18 (targetarrivaltime and targetdeparturetime)? They are both of type TIME according to the header, but I would then expect something like a time value in the output. The first row has "2" and "2" for those values (including quotes). It should be something like 09:42:00 (without quotes).
What do you mean with "limiting the columns"? Do you mean using something like \w80 in mclient or do you mean projecting in the SELECT query?
Can you run the command
Date: 2012-01-04 10:06:46 +0100
(In reply to comment 1)
Projecting the query.
But I just selected on the two time fields, and I'm not happy with what I see.
sql>select targetarrivaltime, targetdeparturetime from kv17;
Date: 2012-01-04 10:07:21 +0100
Created attachment 93
Date: 2012-01-04 10:51:40 +0100
The tuples actually even lack a closing ], so it seems like the reconstruction terminates for the rest of the line.
Date: 2012-01-04 10:53:58 +0100
I would be interested to see what jdbcclient (sorry Java) thinks of this query.
Date: 2012-01-04 12:29:58 +0100
Ok, there's control chars in the output:
(Vim makes it ^@), so the tuples are complete, but the clients get confused since they treat the null-byte as end of the line.
Date: 2012-01-04 12:54:03 +0100
Can you give the result of the queries
Date: 2012-01-04 13:00:02 +0100
(In reply to comment 7)
sql>select cast(targetarrivaltime as interval hour to second) from kv17;
Observe the width of the column above, it is full screen width, don't know if that is cast related.
Date: 2012-01-04 13:10:52 +0100
The problem has to do with negative times.
Date: 2012-01-04 13:23:42 +0100
(In reply to comment 9)
The "funny" thing is... I am not inserting negative times as far as I can see.
Attached will give an indication what goes in...
Date: 2012-01-04 13:25:11 +0100
Created attachment 94
Attached contains the SQL statements that are used to insert the data. Sadly I have no clue how I can get 'marked up queries' so the field values are not 'escaped', but as you can see those are normal times.
Date: 2012-01-04 13:39:33 +0100
I see that not all rows get values for the two times. Do you have a default value for those columns? I'm guessing you don't, and that therefore the values that are actually inserted are cast(null as time).
Date: 2012-01-04 14:03:22 +0100
(In reply to comment 12)
No default values are in there. NULLs are allowed.
Date: 2012-01-04 14:59:58 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=29e91cf9f4f1
Date: 2012-01-04 15:01:51 +0100
I just committed a fix which makes that the query runs.
Date: 2012-01-04 15:03:19 +0100
The bug also occurs in Dec2011.
Date: 2012-01-04 16:27:29 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c0edd6cd8ecf
Date: 2012-01-04 16:29:39 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6e6b3637b011
Date: 2012-01-04 16:31:52 +0100
Date: 2012-01-04 16:32:31 +0100
Fixed in Dec2011 branch.
Date: 2012-01-26 15:32:02 +0100
The Dec2011 version has been release, so declaring this bug as FIXED.
The text was updated successfully, but these errors were encountered: