| From: | chris(dot)gamble(at)CPBINC(dot)com |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Seeking advice on database table design for storing images |
| Date: | 2003-02-07 16:18:56 |
| Message-ID: | 00CA54A79070D411A9E20090273CEF1C14F940@inet1.cpbinc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I am working on an application that will store images with every product
ordered from a given company. Doing this type of application on other
databases, I have always been told to use a seperate table for the image
store. Doing this has given me the table designs listed below. My question
is: Is it within the design of postgres 7.3 to store 30k to 1mb images in a
bytea field, and if so can the two tables below be joined into a single
table without suffering adverse effects?
TABLE - tdatInvoiceLineItems
invoiceid int8
productid int4
quantityordered int4
samplestocustomer int4
adcost numeric 10,4
adheight float4 4
adwidth float4 4
workorderid int8
objectid int8 8
needsart bool
TABLE - tdatCustomerArt
lineitemid int8
artwork bytea
extension varchar
Chris Gamble
CPB Inc
p: 972-579-1642 x 22
f: 972-579-1355
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arjen van der Meijden | 2003-02-07 16:30:06 | Re: Seeking advice on database table design for storing |
| Previous Message | Tom Lane | 2003-02-07 15:41:44 | Re: Pg_dumpall problem[2] |