Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>ok, for a two-table solution, the union sql would look something like this:</p> <p>admin users would use:</p> <pre><code>select id, column1, column2, age from oldrecs union select id, column1, column2, age from newrecs order by age </code></pre> <p>This is a single query and will return a single result set. Note that select blocks have the same field count and type. In your case, both tables will have same layout.</p> <p>Meanwhile your website users would only use last part of that query:</p> <pre><code>select id, column1, column2, age from newrecs order by age </code></pre> <p>Besides this, you'll need a cron job to move aged records from newrecs table to oldrecs table.</p> <pre><code> insert into oldrecs select id, column1, column2, age from newrecs where age &lt; date(now()) - interval 7 days; delete from newrecs where age &lt; date(now()) - interval 7 days; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMySQL Horizontal Partition by Age
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTuncay Göncüoğlu
    1. USTuncay Göncüoğlu
    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. VTDownMod
    1. COI'm pretty sure this does not do what I'm asking for. Instead this just separates a single table into 6 different partitions in a round robin fashion based on the month. What I'm looking for would actually need only two partitions, one that always has the last two weeks of records and one that has anything older then two weeks.
      singulars
      1. PO
      1. USrobhasacamera
    2. COit was the example given in mysql documentation, I was assuming you'd tailor the example for your own situation. however thinking of it, I see a problem. the system you suggest would require mysql to move data from first partition to second one, as records get older, every day. this I dont see happening. you might want to consider using two tables, like newrecs and oldrecs, of same format, giving your normal users results from only newrec table, and giving your admin stuff results from oldrecs union newrecs. and then in a cron job, move records that got old that day to the other table.
      singulars
      1. PO
      1. USTuncay Göncüoğlu
    3. COThat's along the lines I was thinking for a work around. However the admins will need to see items from both the new table and the old table and I'm not sure how to join separate tables together to add more rows and not more columns. I am wondering if there is a way to create two separate partitions and just manually move items from one partition to another using a cron job. That would do the same thing without a nasty join needed.
      singulars
      1. PO
      1. USrobhasacamera
 

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