pippin wrote: > Umm... Sorry but I don't concur. this is not the 80s anymore, how the UX > of a system behaves must not be defined by its database design. You may > want to adapt the database design to make implementation of your > intended UX easier or even astilbe at all but in no cases do you do a > certain broken UX just because that's how your database works. > > One simply doesn't do that. At least not on systems that are supposed to > jot totally suck.
You either fix (or fill in) the missing data in the database at scan time, or else you fiddle-fuck around forever trying to monkey-rig your code to deal with inconsistent data. Trying to do the latter is an endless task filled with inefficiencies and bugs that can never be fully fixed. ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=103476 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
