I think the primary issue is your IN Value in your Table lookup configuration. You have @value. What is wanted here is the name of the field in the DB (probably result set – use the ellipses button to see what is available). This is the field that will be matched with some value.
I have a case where I have a month name and number table with column names “name and number”. For my Table Lookup my In value is “name”. If I wanted to look up based on number, I would need another configuration using “number” as the In value.
In addition, I think your dblookup as coded will only return one tuple. If that is what you want, fine, but I think you want multiple tuples. In that case you need to use the -maxrow switch. If you use that switch and do not provide a value ALL tuples will be returned.
However, what is returned is a string with each column separated by a comma and each tuple terminated with hex 0d0a. In my mind that is not the best data to work with. Give a table with abbreviated Month name and number ( like this Jan 01, etc.) executing :
dblookup -maxrow month_all_rows.tbl “Jan” I get back this:
Jan,01
Feb,02
Mar,03
Apr,04
May,05
Jun,06
Jul,07
Aug,08
Sep,09
Oct,10
Nov,11
Dec,12
Which in hex looks like this:
hcitcl>oth_data2hex $stuff
0000000: 4a61 6e2c 3031 0d0a 4665 622c 3032 0d0a Jan,01..Feb,02..
0000010: 4d61 722c 3033 0d0a 4170 722c 3034 0d0a Mar,03..Apr,04..
0000020: 4d61 792c 3035 0d0a 4a75 6e2c 3036 0d0a May,05..Jun,06..
0000030: 4a75 6c2c 3037 0d0a 4175 672c 3038 0d0a Jul,07..Aug,08..
0000040: 5365 702c 3039 0d0a 4f63 742c 3130 0d0a Sep,09..Oct,10..
0000050: 4e6f 762c 3131 0d0a 4465 632c 3132 Nov,11..Dec,12
I find using the -metacolumname switch gives me what I consider a much easier to work with keyed list like this:
{RSMETACOLUMNNAME {{name} {number}}} {RSDATA {{{Jan} {01}} {{Feb} {02}} {{Mar} {03}} {{Apr} {04}} {{May} {05}} {{Jun} {06}} {{Jul} {07}} {{Aug} {08}} {{Sep} {09}} {{Oct} {10}} {{Nov} {11}} {{Dec} {12}}}}
The RSDATA Key has the data values as a list of lists, the RSMETACOLUMNNAME key tells me which order the columns are in and what their names from the DB are.
By the way, if you are unilaterally returning multiple tuples (using * in your SQL), the value you provide (in my case “Jan”) does not matter, you are going to get the entire result set. I am not sure you can control where the retrieval from the DB begins – perhaps with a specific SQL Statement or Stored Procedure – I have not experimented with that.
So, if the maximum number of tuples returned turns out to be too large and you want to break the retrieval up into more manageable chunks, I am not sure if you can do that or how.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.
.
