Comment 8 for bug 1813191

I ran into a call number (in a real database) that breaks the view if the underlying call number row is referenced: "14.11.01":

select label from asset.call_number where id = XXX;
select * from reporter.asset_call_number_dewey where call_number = XXX;
ERROR: invalid input syntax for type double precision: "14.11.01"

As that would terminate any query that processes a row with such a value, I think more error-guarding is needed.