in reply to Re^2: HoH keys with trailing white spaces ????
in thread HoH keys with trailing white spaces ????

You sound like a grasshopper, who prefers to be a grasshopper all his life.

I have of course no idea whether changing the type of the column benefits your company. And with your attitude, neither will you.

What's the worst that can happen? That you find out why the column has type CHAR(N) instead of VARCHAR(N)?

  • Comment on Re^3: HoH keys with trailing white spaces ????

Replies are listed 'Best First'.
Re^4: HoH keys with trailing white spaces ????
by 3dbc (Monk) on Dec 12, 2011 at 22:56 UTC
    Mr Starbucks,

    What if the existing application (.net, ASP etc.) has been built to consume the char column as is, will changing to varchar blow up the entire system all because we don't want some stupid spaces in the default HoH select (without chopblanks set), which may or may not conform to MSSQL datatype best practices?

    Maybe I should pitch rebuilding the entire system because the foundation is crooked??? If so, now you're starting to sound like a dentist....
[reply]

In Section Seekers of Perl Wisdom