I'm designing a database schema in which I should allow user to create
custom fields at the application level. My application is a web-based
system and it has multiple companies in a single database. So this means
that each company can create their own custom fields. A custom field
created in a company should not be visibile to the other company. Also, we
don't want to restrict the number of fields allowed to create.
I also read some article which talks about the type of patterns:
My question here is, what is the best approach to define the architecture
for custom fields. Performance should not be compromised.
Thank you in advance.
View this message in context: http://www.nabble.com/Custom-Fields-Database-Architecture-tp24034270p24034270.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
pgsql-general by date
|Next:||From: James B. Byrne||Date: 2009-06-15 14:22:10|
|Subject: Re: cygwin and postgresql|
|Previous:||From: Merlin Moncure||Date: 2009-06-15 13:02:24|
|Subject: Re: help with data recovery from injected UPDATE|