BIND 10 #807: Improve error message when unknown type encountered

[BIND 10 Development]

#807: Improve error message when unknown type encountered
-------------------------------------+-------------------------------------
                 Reporter:  stephen  |                Owner:
                     Type:           |               Status:  closed
  enhancement                        |            Milestone:
                 Priority:           |  Sprint-20110419
  critical                           |           Resolution:  wontfix
                Component:           |            Sensitive:  0
  b10-auth                           |  Add Hours to Ticket:  0
                 Keywords:           |          Total Hours:  0
Estimated Number of Hours:  2.0      |
                Billable?:  1        |
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by jreed):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I am closing this. The description here is too vague. And I am pretty sure
 the initial argument was misunderstood.

 From jabber on March 25 (while in our meeting):

 {{{
 (05:13:04) jreed: Error loading database: database is locked
 (05:13:35) jreed: is what was reported; that is the bigger issue. There
 was a new
  ticket created for that.
 (05:13:48) jreed: The unclear error never even got shown due to the bigger
 issue.
 (05:14:55) jreed: And jinmei already provided a patch to fix that too.
 (05:16:13) jelte at jabber.isc.org: the actual error from b10-loadzone is
 much
  clearer than what came by on the list, btw
 (05:16:24) jreed: Yes, definitely.
 (05:16:34) jelte at jabber.isc.org: Error loading database: Error while
 loading
  tjeb.nl.: Cannot parse RR: tjeb.nl. 3600 IN AXEE ext.ns.whyscream.net.
 (05:16:43) jreed: Exactly. That is clear. :)
 (05:16:45) jelte at jabber.isc.org: so the problem may not even exist indeed
 :)
 (05:16:54) jelte at jabber.isc.org: but i saw something like 'parameter
 error'
 (05:17:19) jreed: loadzone is broken as it is.
 (05:17:29) jelte at jabber.isc.org: it could be a *little* bit clearer if it
 said
  that it's not 'just' a parse error but really an unsupported type, but oh
 well
 }}}

 Let's ignore this for now. It is not critical and we don't want to keep
 wasting time on loadzone -- unless we re-decide to keep existing loadzone.
 (Note we need to use the pydnspp for our new loadzone.)

-- 
Ticket URL: <http://bind10.isc.org/ticket/807#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development