From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: Encountered an error |
Date: | 2016-03-10 22:03:19 |
Message-ID: | 20160310220319.GR9358@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Fri, Mar 11, 2016 at 01:16:33AM +0530, Shaan Repswal wrote:
> I am new to databases and am a novice to programming in general.
Don't worry.
> @Karsten - I know, I got the feeling that the design felt awry as well. The
> database will be on the local machine. And the client side will have the
> code to error check the column names being added and also if there already
> is a column by this name or not.
You can add a second table (pseudo code)
inventory_detail
pk serial primary key
fk_inventory integer foreign key (inventory.pk)
detail_name text
detail_value text
and then - instead of creating columns in table inventory -
add rows to the inventory_detail table where .detail_name
would hold what otherwise would be the column name of the new
column in inventory and .detail_value the value you would
have put into the new column in table inventory. The
fk_inventory column would hold the primary key of the row in
the inventory table this inventory_detail row belongs to.
Just a suggestion.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Sawyer | 2016-03-13 01:23:40 | unable to connect to postgres db via psycopy |
Previous Message | Adrian Klaver | 2016-03-10 20:49:28 | Re: Encountered an error |