Skip site navigation (1) Skip section navigation (2)

Re: layout question

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: layout question
Date: 2010-06-14 14:27:37
Message-ID: 4c163c5c.c32ce70a.68bf.ffffa80b@mx.google.com (view raw or flat)
Thread:
Lists: pgsql-novice
On Sat, Jun 12, 2010 at 10:56:34PM +0200, Jean-Yves F. Barbier wrote:
> Hi list,
> 
> I must build a kind of ERP and I wonder what's the best DB layout,
> especially about quotations/orders/delivery orders/invoices/RMAs/credit
> notes.
> 
> It must be very scalable (say from 10 invoice a day to 2,000 or even more.)
> 
> As these docs' structures are very close, what is the best:
> to have one table per kind of doc and to copy info from one to another,
> or to have only one table with a flag telling the doc's type and external
> sequences to keep numbering coherent? (also means the docs' lines table
> will be pretty huge.)

Have you considered using one of the ERP packages already available? For
instance, one of those listed here:
http://en.wikipedia.org/wiki/List_of_ERP_software_packages

Your specific question can be generalized somewhat: given a requirement to
store records of several closely related types, is it best to store them all
in one table, or separate, per-type tables. You're likely to find several
different answers, depending on whom you're asking. A few key points to
remember: 

* Make sure your model allows you to create meaningful constraints
* Avoid the temptation to use PostgreSQL's inheritance mechanism for this
  purpose.

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

In response to

pgsql-novice by date

Next:From: Joshua TolleyDate: 2010-06-14 14:30:48
Subject: Re: Global temporary tables surprise
Previous:From: Didier Gasser-MorlayDate: 2010-06-14 07:42:46
Subject: re Layout question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group