Stupid database tricks
Are there any vertical market software vendors who can design a decent database? If I see a field called "portfolio_id", I think it's reasonable to expect it to be a foreign key to a table called "portfolio", which has a primary key that's also called "portfolio_id". "portfolio_id" should not be the primary key of a table called "account_to_product_portfolio".
For that matter, there should never be a table called "account_to_product_portfolio". There also shouldn't be 1,700 tables in one database. I half-suspect that a design goal in the database was to frustrate clients enough that we'd stick to the API.
At least these people use actual foreign keys, which is more than I can say for their predecessor.
For that matter, there should never be a table called "account_to_product_portfolio". There also shouldn't be 1,700 tables in one database. I half-suspect that a design goal in the database was to frustrate clients enough that we'd stick to the API.
At least these people use actual foreign keys, which is more than I can say for their predecessor.
