Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are 3 approaches:</p> <ol> <li><p>Store invoices and quotes in separate tables.</p> <p>This is a good design if invoices and quotes have few fields in duplicate (otherwise, use option #3 with 3 tables), and if there's a 1-many or many-many relationships between them (for 1-1, use option #2). </p> <p>This is also a good choice if it's common that "shared" information between the two can actually mutate when the quote becomes the invoice (although some of these mutations should be properly handled with separate fields/tables, such as applied discounts, etc...).</p> <p>A slight variation of this option is obviously needed be done when multiple quotes are turned into a single (or multiple) invoices. This adds a 3rd table which is a mapping between a set of quotes and an invoice (or set of invoices if it gets that complicated) for them.</p></li> <li><p>Store them in the same table, with extra flag "Invoice or quote" and any extra fields from both stored. This can be done with either invoices and quotes in distinct rows, or with them sharing rows (with flag having "both" value too).</p> <p>The latter (same row can be both invoice and quote) is a good choice <strong>if they are mapped 1 to 1</strong>, and there are few fields that distinguish the two. </p> <p>The former (separate rows for invoices and quotes) is not a vary good design in general and better done with the #3 or #1 options.</p></li> <li><p>Have 3 tables, one for common fields between the two, and two for invoice-only and quotes only.</p> <p>This is a good choice if invoices and quotes are mapped 1-1, or if they are 1-many but each of the many invoices has exactly the same field values for whichever fields are common. Otherwise, use #1.</p> <p>A slight variation of this option can be done when multiple quotes are turned into a single invoice. This adds a 4th table which is a mapping between a set of quotes and an incoice (or set of invoices if it gets that complicated) for them. Again, the assumption here is that there's a sizeable chunk of common info between all of the quotes and invoices linked/combined together, otherwise just go with #1.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POInvoicing vs Quoting or Estimating
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDVK
    1. USDVK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POInvoicing vs Quoting or Estimating
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 The first option seems best. Jobs < Orders(Quotes), Invoices; Invoices < Payments.
      singulars
      1. PO
      1. USPetrus Theron
    2. CO+1: Options 1 & 3 are my picks. We have a database with Quote and Invoices in the same table and a single flag to differentiate between the two. I'm not in favor of this. However, a consideration is that when paying for server space and data transfer (as our application depends), this approach gains weight.
      singulars
      1. PO
      1. USIAbstract
    3. CO@dboarman-FissureStudios - Option #3 should take care of that last consideration - it normalizes away the common data from option #1
      singulars
      1. PO
      1. USDVK
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload