262 reputation
13
bio website stackoverflow.com
location London, United Kingdom
age 45
visits member for 1 year, 8 months
seen Apr 11 at 17:19

.


Aug
18
awarded  Yearling
Jul
2
comment Multiple Database Design or NOT?
@Jacques: Yes, partitioning can happen at a later stage.
Jul
2
answered Multiple Database Design or NOT?
May
9
answered Slow query joining on subqueries with max
Feb
16
awarded  Supporter
Feb
15
answered Normalization of DB
Feb
15
comment Normalization of DB
@ashofphoenix: Why do you have a separate table for user_profile? Can one login have more than one profile?
Feb
15
comment Normalization of DB
@dev: the original version of the image can be found here: i.stack.imgur.com/k9klv.png (If you have editing privileges, you can edit the question to see the url.)
Aug
18
comment Database table and NULLs
Nothing would stop you having a separate table, but it would be a bad choice, for a number of reasons. Assuming that all accounts could potentially be closed, but each account can only be closed once, then the AccountClosure record has the same key as the Account record - it therefore makes sense to have them on the same record. This makes it easier to write queries that require the closure date (fewer tables in such queries), fewer tables in the database schema overall (simpler maintenance) and less filespace used (account ID only stored once for each account, including closures).
Aug
18
awarded  Autobiographer
Aug
18
awarded  Teacher
Jan
10
answered Inventory Database Design Issue
Jan
4
answered Database table and NULLs
Dec
19
answered Oracle sort varchar2 column with special characters last