Invalid column name assertion failure
F142 - Failure Feedback Forum
% view a:0 def 1 | dump
Failed assertion at src/column.c, line 475: 0
Can the columns be validated rather than assertion failure?
Summary
Fixed and committed to darcs.
Imported
Returning a "sane error" from this level turns out to be harder than I thought. I'm going to have to leave things as is for now, I'm afraid.
I ran into this when doing an oracle select using the oratcl operator at http://www.vlerq.org/vqd/368. For something like "select to_date('HH24:MI:SS', '15:34:00') from dual", the column name in the created view will get contain the entire to_date string includinng the colons.
It is easy enough to modify the oratcl operator to throw an error if a colon is encountered in the column name. Thanks for checking.
Hm, been thinking some more. I did find a better spot to check things (metaview conv, not metaview use), and now it throws a generic "invalid view" error. But your colon test is probably a good idea anyway, in case the next letter happens to be a valid Vlerq type.
