One Too Many
-
A table in the live production environment:
CREATE TABLE setPaymentPlans
(
[cppDivision1] [varchar](12) NOT NULL,
[cppDivision2] [varchar](12) NULL,
[cppDivision3] [varchar](12) NULL,
[cppDivision4] [varchar](12) NULL,
[cppDivision5] [varchar](12) NULL,
[cppDivision6] [varchar](12) NULL,
[cppDivision7] [varchar](12) NULL,
[cppDivision8] [varchar](12) NULL,
[cppDivision9] [varchar](12) NULL,
[cppDivision10] [varchar](12) NULL,
[cppDivision11] [varchar](12) NULL,
[cppDivision12] [varchar](12) NULL,
[cppDivision13] [varchar](12) NULL,
[cppDivision14] [varchar](12) NULL,
[cppDivision15] [varchar](12) NULL,
[cppDivision16] [varchar](12) NULL,
[cppDivision17] [varchar](12) NULL,
[cppDivision18] [varchar](1) NULL,
-- Other fields...
)Perhaps they thought adding another table for a one to many relationship would be one too many tables. :rolleyes: Also, you'll note the prefix of "cpp". I guess they changed the name of the table at some point and didn't feel like changing the prefix. Some people really need to learn how to use table aliases. And I have no idea why that last one is a varchar(1) rather than a varchar(12).
-
A table in the live production environment:
CREATE TABLE setPaymentPlans
(
[cppDivision1] [varchar](12) NOT NULL,
[cppDivision2] [varchar](12) NULL,
[cppDivision3] [varchar](12) NULL,
[cppDivision4] [varchar](12) NULL,
[cppDivision5] [varchar](12) NULL,
[cppDivision6] [varchar](12) NULL,
[cppDivision7] [varchar](12) NULL,
[cppDivision8] [varchar](12) NULL,
[cppDivision9] [varchar](12) NULL,
[cppDivision10] [varchar](12) NULL,
[cppDivision11] [varchar](12) NULL,
[cppDivision12] [varchar](12) NULL,
[cppDivision13] [varchar](12) NULL,
[cppDivision14] [varchar](12) NULL,
[cppDivision15] [varchar](12) NULL,
[cppDivision16] [varchar](12) NULL,
[cppDivision17] [varchar](12) NULL,
[cppDivision18] [varchar](1) NULL,
-- Other fields...
)Perhaps they thought adding another table for a one to many relationship would be one too many tables. :rolleyes: Also, you'll note the prefix of "cpp". I guess they changed the name of the table at some point and didn't feel like changing the prefix. Some people really need to learn how to use table aliases. And I have no idea why that last one is a varchar(1) rather than a varchar(12).
FTFY :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).