BIND 10 #2586: sqlite3 data source doesn't seem to handle escaped name correctly

[BIND 10 Development]

#2586: sqlite3 data source doesn't seem to handle escaped name correctly
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  data source   |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130219
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  4             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:7 jelte]:
 > hmz, it fails for me:
 [...]
 > (the other one works)
 >
 > If we just want to 'fix' the test, we could use '!.no.example.com'
 instead of '%.no.example.com', which passes here. But it would appear
 there is more wrong in the handling here (unpexpected behaviour around '%'
 in sql context is worrying)...

 Ah, okay.  It didn't happen to me, so it may depend on the version of
 SQLite3, but I can see the possibility.  I just changed it to ! in the
 test.  This test is not for checking behavior with these unusual
 characters, so it makes sense to use safer characters anyway.

 As for the use of % in SQL-based data sources, I guess we'll need to
 defer it to revisiting the label representation in SQLs.

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