Error in constant search condition for CONTAINS not detected until compilation time. - by Erland Sommarskog

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 640240 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 1/29/2011 10:56:00 AM
Access Restriction Public


If you have a constant search condition for CONTAINS in a stored procedure, the procedure is created. It is not until the optimizer builds a query plan that the error is detected. This means that a silly typo  may go undetected until a later phase in development, meaning extra cost and delay.
Sign in to post a comment.
Posted by Microsoft on 2/1/2011 at 5:23 PM
Hi Erland,

Thank you for reporting this. You're right - parsing of fulltext search queries isn't done until compile time. Moving the parsing logic to binding time will be a fair bit of effort. We'll investigate doing this in a future release.