Seeking advice on database table design for storing images
От | chris.gamble@CPBINC.com |
---|---|
Тема | Seeking advice on database table design for storing images |
Дата | |
Msg-id | 00CA54A79070D411A9E20090273CEF1C14F940@inet1.cpbinc.com обсуждение исходный текст |
Ответы |
Re: Seeking advice on database table design for storing
Re: Seeking advice on database table design for storing images |
Список | 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
В списке pgsql-general по дате отправления: