The Weird and The Wonderful

PIEBALDconsult wrote:

And I write it as

namespace mystuff.otherStuff
{
//---------------------------------------------------------------------------------------
/// <summary>
/// This is where I do database stuff
/// </summary>
//---------------------------------------------------------------------------------------
public static class MyDbConstants
{
private const string SQL1 = 
@"
SELECT ID
, NAME
, BIRTHDAY
FROM TABLE
WHERE NAME LIKE @PARAM
" ;

private const string SQL2 = 
@"
SELECT ID
, NAME
, BIRTHDAY
FROM TABLE_OTHER
WHERE NAME LIKE @PARAM
" ;

private const string SQL3 = 
@"
SELECT ID
, NAME
, BIRTHDAY
FROM TABLE_OTHER2
WHERE NAME LIKE @PARAM
" ;

// 100 other like the above with increasing complexity.

PIEBALDconsult wrote:

No, I don't use consts for
SQL.

PIEBALDconsult wrote:

I meant "that".

Brady Kelly wrote:

Looks pretty damned neat to me.

PIEBALDconsult wrote:

so it prints out nice in error messages.

const string sql = "select stuff "+
    "from table"; // Best practice doesn't apply to consts

KRucker wrote:

The "Best Practice" is not to use string concatenation in a loop.

KRucker wrote:

The concatination(sic) that you are showing should be fine, unless it is being performed in a loop.

Chad3F wrote:

After all, at one time, how many people had the opinion the world was flat and
the best practice was not to sail too far out?

Chad3F wrote:

and happens to be useful (i.e. less lost lives/cargo), doesn't justify the basis

Chad3F wrote:

Teach that same person 10 concepts, with understanding, and now they know 100's or even 1000's of things (i.e. the meaningful combinations of those 10 concepts)

.field private static literal string SQL = string('SELECT   ID,   NAME,   BIRTHDAY FROM   TABLE WHERE   NAME LIKE @PARAM')