From: | mstory(at)uchicago(dot)edu |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Front Ends |
Date: | 2004-11-27 04:35:45 |
Message-ID: | 1101530145.41a80421530e7@churlish.uchicago.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am new to the databasing market, and am currently working on a complex
database that relies heavily on dynamically created tables for data storage. My
partner and I have therefore been trying to find a front end utility that can
handle using tables with names that aren't known at compile time. A few questions:
1. is this architecture (relying heavily on dynamically created tables) sound
enough to yield a production quality database?
2. What front end language/utility could handle the dynamic environment of this
database ( my partner and i have looked into ruby on rails/zope/zul and java),
and still yield a production quality product? Are any of the above proposed
solutions better than the others? And if anyone has experience with these, are
they capable of handling multiple dynamically created tables?
Thanks
Matthew Story
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Welty | 2004-11-27 04:59:19 | Re: Front Ends |
Previous Message | Kamil Kaczkowski | 2004-11-27 02:20:16 | Re: row-level deadlock problem |