network profile
| bio | website | totalgood.com |
|---|---|---|
| location | Kota Kinbalu, Malaysia | |
| age | ||
| visits | member for | 11 months |
| seen | Apr 3 at 21:44 | |
| stats | profile views | 1 |
Former robotics engineer converted to web developer and opensource contributor--mostly in Python and PHP. I enjoy automating drudgery and augmenting human decision-making with software.
|
Mar 20 |
comment |
Character vs Integer primary keys Thanks. Your question forced me to look at this question more thoroughly than I had in the past (I used to do this your way), and saved me a lot of scalability and speed grief by doing it the standard way. |
|
Mar 20 |
answered | Character vs Integer primary keys |
|
Mar 20 |
comment |
Character vs Integer primary keys @BrianBallsun-Stanton if you have any bulky sequential data that rels to these lookup tables, storage space is not cheap (in terms of query speed) because disk read speed is the bottleneck in any RDB that can't be cached entirely in RAM. I found this while trying to develop an RDB schema that can compete with the best in the time series DB business Full disclosure, I have no relationship to Skyspark, except that they charge my employer a lot for use of their very efficient DB. |
|
Mar 12 |
awarded | Excavator |
|
Mar 12 |
awarded | Editor |
|
Mar 12 |
revised |
Performance implications of MySQL VARCHAR sizes minor typo ("the the"). e.g. filler just for accuracy and to get over the minimum edit-distance threshold |
|
Mar 12 |
suggested | suggested edit on Performance implications of MySQL VARCHAR sizes |
|
Sep 13 |
awarded | Supporter |
