Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The big question is, what will this table be used for? If the only queries are going to be ranges of ORDER_IDs or aggregates on ITEM_IDs, then you just need individual indexes on those columns. Make the QUEUE_ID the primary key (since auto increment ensures the unique and not null anyway). Try the following:</p> <p>Update: As per the OP's comment below, there can be multiple order ids per customer and vice versa, but the combination has to be unique. IMO, it is easier to create a satellite table with the unique constraint satisfied, and use the index from that table in this <code>slots</code> table.</p> <pre><code>CREATE TABLE cust_order ( combo_id int(11) NOT NULL AUTO_INCREMENT, customerid int(11) NOT NULL, orderid int(11) NOT NULL, PRIMARY KEY combo_id, INDEX customerid (customerid), INDEX orderid (orderid), UNIQUE KEY combination (customerid, orderid) ) ENGINE=INNODB; CREATE TABLE `slots` ( `combo_id` int(11) NOT NULL, `queueid` int(11) NOT NULL AUTO_INCREMENT, `item_id` int(3) NOT NULL, `variable1` int(3) NOT NULL, ... ... `variable9` tinyint(1) NOT NULL, PRIMARY KEY `queueid`, INDEX `combo_id` (`combo_id`), INDEX `itemid` (`itemid`), FOREIGN KEY (combo_id) REFERENCES cust_order (combo_id) ) ENGINE=INNODB; </code></pre> <p>You have to run two different insert queries. First, you load the combo table, which takes care of just the numerical index without the satellite data and it should be really fast. Afterwards, when you insert into the <code>slots</code>, lookup via the customerid + orderid will be really fast and you just use the combo_id as the foreign key.</p> <p><strong>Please note</strong> that you must use the InnoDB engine for the Foreign Keys to work.</p>
    singulars
    1. This table or related slice is empty.
    1. POExport/import 50-million row database without the index?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSudipta Chatterjee
    1. USSudipta Chatterjee
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI need to ensure that customerid and orderid are both unique ( there can be multiple customers for one orderid and vice versa ) The high value for auto-increment is the relict of my few imports - I think it's where it came from.
      singulars
      1. PO
      1. USuser3010273
 

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