Self Referencing

Geek Lectures - Things geeks should know about » Blog Archive » Self Referencing

Fri, 04 Jan 2008 09:58:43 GMT

PingBack from http://geeklectures.info/2008/01/03/self-referencing/

VSTS Links - 01/07/2008

Team System News — Mon, 07 Jan 2008 19:14:43 GMT

Joel Semeniuk on Team Based Development Video from TechEd. Sean Lumley on Web tests work at the HTTP...

re: Self Referencing

wtroost — Wed, 09 Jan 2008 22:39:38 GMT

It's kinda hard to see how resolving "dbo.myproc" is harder than "mydb.dbo.myproc". I mean... you know the name of the current database, right?

re: Self Referencing

arabino — Fri, 11 Jan 2008 17:22:14 GMT

It appears that self-references in stored procedures are causing warning only(TSD3025) which can be suppressed using project options. However, self-references in views are causing warning(TSD3024) and error(TSD4001). There is no way an error can be suppressed by project options. Would it be possible to only report a warning(TSD3024) and NOT the error(TSD4001)? I would be able to easily suppress the warning for the self-references in the views/stor. procs using project options.

Here is a reason why I'd like to suppress self-references warnings/errors:

Let's say I import existing production DB into DBPro. I don't want to touch ANY TSQL code on initial import. The reason is that ANY code change will result in full regression testing effort which is very expensive for us. I don't want to clean-up any self-references after the initial check-in. I would rather suppress any warnings about self-references.

Thanks.