From: | Matt Miller <mattm(at)epx(dot)com> |
---|---|
To: | Bob Pawley <rjpawley(at)shaw(dot)ca> |
Cc: | Postgre General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Self creating tables |
Date: | 2005-09-02 17:33:17 |
Message-ID: | 1125682397.3076.12.camel@dbamm01-linux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2005-09-02 at 09:51 -0700, Bob Pawley wrote:
> regarding the setting up of tables
> ...
> I could create a separate table for each category of elements ... The
> challenge is ... a distinct possibility of the user inserting an
> element that we haven’t considered. The above approach would force
> him to stop what he is doing and create a new table(s) for the new
> element(s).
Your application should be able to create tables for the user. The user
should not need to exit your app, get to an SQL command line, and issue
CREATE TABLE statements. The CREATE TABLE statement is just another SQL
statement, like SELECT, INSERT, etc. Try using your API (whatever that
is -- this is another decision you may still have to make) to issue
CREATE TABLE and see how it works.
> in my Postgresql book or through the Postgre on-line help.
Typically the database is referred to either as "Postgres" or as
"PostgreSQL," but not as "Postgre."
From | Date | Subject | |
---|---|---|---|
Next Message | Cristian Prieto | 2005-09-02 18:17:09 | Re: Trouble with bytea in SPI... |
Previous Message | Bob Pawley | 2005-09-02 16:51:12 | Self creating tables |