Incompatibility between compare "in" operator in native speedtables versus stapi-based postgres version

flightaware / speedtables

Speed tables is a high-performance memory-resident database. The speed table compiler reads a table definition and generates a set of C access routines to create, manipulate and search tables containing millions of rows. Currently oriented towards Tcl.

https://flightaware.github.io/speedtables/

BSD 3-Clause "New" or "Revised" License

65 stars 15 forks source link

Incompatibility between compare "in" operator in native speedtables versus stapi-based postgres version #64

Closed lehenbauer closed 8 years ago

lehenbauer commented 8 years ago

Small bug in speedtables' stapi SQL translation when using the in operator: the documentation (https://flightaware.github.io/speedtables/manual/ch05.html) says that in in a -compare switch should be {in field valueList} but https://github.com/flightaware/speedtables/blob/master/stapi/client/pgsql.tcl#L871 treats it as {in field value1 value2 value3...}; we think that L871 should be foreach v [lindex $tuple end]

resuna commented 8 years ago

Fixed in branch "issue64".

bovine commented 8 years ago

merged into master for upcoming 1.9.4 release