sql server - Adding ghost data in a pretty way -


this kinda hard explain.

our client wants able add "fictional data" or "ghost data". data shouldn't show unless explicitly defined. able "what if had delivery @ address". (which don't wanna pretend did)

my first thought add boolean column tell whether entry ghost entry. means we'd have include constraint every stored procedure. or linq query we've every written , write. not solution.

another idea coworker had creating duplicate table containing ghost data. way can keep them separate. problems arise once realize there's relationships table. these has duplicated too. , maintainability takes hit cause every change make in normal table have reflected in "ghost" table.

ideas?

you can create duplicate tables. - of course every table potentially hold ghost data need seperate table.

to around problem relations need joins against unions of real , ghost data.

edit: example


Comments

Popular posts from this blog

Unable to remove the www from url on https using .htaccess -