Timeline for Large accounting table, best way to partitioning by two dates
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2012 at 20:20 | answer | added | Rick James | timeline score: 2 | |
| Mar 19, 2012 at 17:51 | history | tweeted | twitter.com/#!/StackDBAs/status/181800026480197632 | ||
| Mar 19, 2012 at 15:27 | history | migrated | from stackoverflow.com (revisions) | ||
| Mar 19, 2012 at 11:48 | answer | added | Clodoaldo | timeline score: 2 | |
| Mar 19, 2012 at 9:09 | comment | added | Radu Maris | @Darhazer Unfortunately I can't use InnoDB, but according to dev.mysql: "For MyISAM tables, if there are no free blocks in the middle of the data file, concurrent SELECT and INSERT statements are supported", I was assigned to another project, now i'm back to this, I am redesigning and I will update the question in the following days. | |
| Mar 10, 2012 at 15:41 | comment | added | Darhazer | Use InnoDB engine - it provides row-level locks and is faster for insert/update intensive applications. You don't need index on user, since it's the left-most field in the primary key and primary key can be used to resolve any query filtered by user. I guess prim_ipv6 has to be UNIQUE, as the primary key is unique and this is the v6 version of pk | |
| Mar 5, 2012 at 8:45 | history | asked | Radu Maris | CC BY-SA 3.0 |