Removing PARSENAME from sys.schemas lookup in DropClass procedure

[Prof-hu]

Proposed solution to issue #5

[mbt1]

Implementing this would change documented behavior and potentially break many tests for other tSQLt users.

[Prof-hu]

@mbt1

Implementing this would change documented behavior and potentially break many tests for other tSQLt users.

What is the exact behavior that is referenced here? Can you point me to that section in the documentation?

[mbt1]

The expected behavior is that you can pass in names with and without brackets. The PARSENAME function is the only reliable way to remove those brackets for further processing. Your other comment however tells me that there is a test missing. I will look into that.

[Prof-hu]

@mbt1

The expected behavior is that you can pass in names with and without brackets. The PARSENAME function is the only reliable way to remove those brackets for further processing. Your other comment however tells me that there is a test missing. I will look into that.

I see. Then probably PARSENAME should be used at all the other WHERE clauses. It would still not work with a schema name with a dot in it supplied without brackets, but at least would work with brackets. :D

I just experimented with this a little and seem to work OK, so created another pull req with this version.