Wow, that is ... SO ... much simpler than the direction I was going.

That will work quite well ... Thank you !

I think I could get a series of numbers using another table in the DB as something like: select row_number() over () as rownum from esn limit 15999 however, how would you fill in the values? I *think* something like: select id, c as values from (select id, low_esn c from udr_range union all select i...

I have a table that looks like: id | low_esn | high_esn ------+---------+---------- 101 | 15900 | 15999 102 | 15900 | 15999 103 | 15900 | 15999 what I need to do is convert this to : id | values -----+-------- 101 | 15900 101 | 15901 101 | 15902 ... 101 | 15998 101 | 15999 102 | 15900 102 | 15901 10...

Late followup:

Installed pyodbc 3.0.7 and the problem is no longer present.

It is on a RHEL 5.6 server. I had just downloaded pyODBC yesterday. I had downloaded pyODBC 2.1.6 because that is what the Vertica docs says is the version supported.

I will give the patched version a try later today

I am trying to figure out how to connect to Vertica with pyODBC and am having some problems with the returned rows just being garbage. Using: Vertica 7.0 Python 2.4.3 pyODBC 2.1.6 From vsql: [dbadmin@vertica1 dan]$ vsql -c "select node_name, node_state from v_internal.vs_node_states" node_name | nod...