SQL Server Team-based Development - Red Gate Software

1
GO
SELECT UserId ,
UserName ,
UserPassword ,
IsActive ,
IsDeleted ,
IsSleeping
FROM Users
WHERE IsActive = 1
AND IsSleeping = 1
Listing 11-19: Refactoring the DDL to avoid the "Tell, don't ask" anti-pattern.
347
Chapter 11: SQL Refactoring
By moving each status code to its own column, we don't have to keep the data in code;
it's stored in the schema like it should be. It also means that we can mix and match the
different statuses, as required.
There are times when you might still use the "data in code" method, but it should be
used only with caution. For example, we might consider using it if the UserStatus
values really were static and used through multiple applications. I still don't like it,
though. The hard part is changing your thinking processes so that you know when it's
still needed and when it isn't.
Summary
In this chapter, we've looked at why refactoring is important, in the context of the
broader picture of database development. Refactoring allows us to improve the
performance, maintainability, and security of database code, without affecting any
of the systems that access the database code.
In order to do this, we need a set of unit tests that cover our database functionality,
a database abstraction layer that isolates the underlying structure from the outside