![]() | |
#91
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#92
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#93
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#94
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#95
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#96
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
#97
| |||
| |||
|
|
This is a business-logic question, not a data question. The database should not be storing how to use a column in another column. That is not data modeling. (All generalizations disclaimed with "usually".) |
![]() |
| Thread Tools | |
| Display Modes | |
| |