Hello,
I need some comments or advices regarding different tables designs
approach, for two part of our needs.
_*User saved forms*_
in our project, we want to give to our users ability to save form fields
values for later use. It will be named the fast OR saved searches. The
user can save
I'm facing a very similar problem where I work (local govt) where we
want to put around 100 forms online. The idea of 100 seperate database
tables is too painful to contemplate.
Depending on the nature of the data, I suppose, both the structured text
string and the serialised object options
Bruno Lavoie wrote:
We have a relatively huge number of search forms, each one with specific
fields. So I don't want, if possible, to use a distinct table for each
form.
This is one of the few areas where storing XML in a relational database
seems to make sense to me. Forms are well suited to
On Fri, Jul 25, 2008 at 8:35 AM, Bruno Lavoie [EMAIL PROTECTED] wrote:
The hesitation here is : how to store the fields values pairs, in
FIELDS_VALUES?
Check out contrib/hstore:
http://www.postgresql.org/docs/current/static/hstore.html
--
Sent via pgsql-general mailing list
