Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have built a large reservation system for travel operators and wholesalers, and I can tell you that it isn't easy. There seems to be similarity yet still large differences in the kinds of product booked. Also, date-sensitivity is a large difference from other systems.</p> <p>1) In respect to 'customers' I have typically used different models for representing different concepts. You really have:</p> <ul> <li>a. Person / Company paying for the booking</li> <li>b. Contact person for emergencies</li> <li>c. People travelling</li> </ul> <p>a &amp; b seem like the same, but if you have an agent booking, then you might want to separate them. </p> <p>I typically use a => 'customer' table, then some simple contact-fields for b, and finally for c use a 'passengers' table. These could be setup as different associations to the same model, but I think they are different enough, and I tend to separate them - perhaps use a common address/contact model.</p> <p>2) I think this is fine, but depends on your needs. If you are building up itineraries for a traveller, then it makes sense to setup 'passengers' on the 'reservation', then for individual itinerary items, with links to which passenger is travelling on/using that item.</p> <p>This is more complicated, and you must be careful to track dependencies, but the alternative is to not track passenger names, and simply assign quantities to each item (1xAdult, 2xChildren). This later method is great for small bookings, so it seems to depend on if your bookings are simple, or typically built up of longer itineraries.</p> <p>other) In addition, in respect to different models for different product types, this can work well. However, there tends to be a lot of cross over, so some kind of common 'resource' model might be better -- or some other means of capturing common behaviour.</p> <p>If I haven't answered your questions, please do ask more specific database design questions, or I can add more detail about specific examples of what I've found works well.</p> <p>Good luck with the design!</p>
    singulars
    1. This table or related slice is empty.
    1. POPerformance issues with complex nested RoR reservation system
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USadzdavies
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPerformance issues with complex nested RoR reservation system
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks @adzdavies, some useful pointers. I have pondered this issue about customers at length. From a design perspective, it would be much simpler to handle these as separate models. However, it would also be extremely useful to have a central contact list. I'm still debating over the product types. I'm wondering of single table inheritance would allow me to cover the commonalities, while still allowing me to accommodate the differences. I'm not too familiar with STI, so will need to research this.
      singulars
      1. PO
      1. USAndy Harvey
    2. COone more, what do you mean by 'date sensitivity'?
      singulars
      1. PO
      1. USAndy Harvey
    3. COJust the need to track dates per booking. The inventory is not simply a number in stock, but how many spaces on a given date.
      singulars
      1. PO
      1. USadzdavies
 

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