[SQL] Two tables or three?

I'm designing a schema for an app that requires two large blobs per row. Given that querying does not hit those, I presume it is beneficial to move the blobs out of the main table. But should each blob be in its own table, or should they go into a single, three column table? The main table does

Re: [SQL] Aggregate versus lineitem report

On Fri, Oct 21, 2005 at 11:32:13 -0400, Jerry Blumenthal <[EMAIL PROTECTED]> wrote: > How do you get a report that lists items and then produces a sum at the > end. Like this: > > name date amount1 amount2 > name date amount1 amount2 > name date amount1 amount2 > > tot

Re: [SQL] Two tables or three?

James Cloos <[EMAIL PROTECTED]> writes: > I'm designing a schema for an app that requires two large blobs per > row. Given that querying does not hit those, I presume it is > beneficial to move the blobs out of the main table. You shouldn't contort your schema artificially in order to do that. P

Re: [SQL] Two tables or three?

> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes: Tom> You shouldn't contort your schema artificially in order to do that. Tom> Postgres automatically stores wide fields out-of-line ... Cool. Good to know it is even better than I thought. :) -JimC -- James H. Cloos, Jr. <[EMAIL PROTECTED]>