meta user
network profile
| bio | website | |
|---|---|---|
| location | Indore, India | |
| age | 22 | |
| visits | member for | 8 months |
| seen | Feb 6 at 7:47 | |
| stats | profile views | 2 |
I am from Electronics and communication back ground, and knows C/C++ and Embedded very well, Now I am in PHP web development and Programming is my interest and as I am working on Web development, I want to use and learn latest technology and implement them as nicely as it can.
I love to help people on programming especially on logics, and also to learn new concepts and discussions. :) Thank you ;)
|
Oct 19 |
comment |
Partitioning a table vs moving entries to another table Thanks for your further explanation, Now I get the concept of this :) |
|
Oct 10 |
awarded | Supporter |
|
Oct 10 |
comment |
Null Values and Performance Thanks @Chris, As I mostly use InnoDB Engine and In case of breaking tables for the sake of not having NULL Values will also include many JOINS while retrieving and that will lead to the extra disk I/O as InnoDB will probably do a sequential index scan. Is that approximate to what you mean to say? |
|
Oct 9 |
comment |
Null Values and Performance I am a beginner in this, As having NULL values use full table scan if we do a ORDER BY (if I am correct) and I am having all most all query on the table with ORDER BY clause That's why for the sake of Performance I try to avoid NULL Values or Empty strings and move them to another table using relation, so if there is NULL or Empty string then it will not have any entry of that information. BUT I am not sure about the performance part when there is no sense in keeping that info in another table |
|
Oct 9 |
asked | Null Values and Performance |
|
Sep 23 |
awarded | Scholar |
|
Sep 23 |
accepted | Partitioning a table vs moving entries to another table |
|
Sep 22 |
comment |
Partitioning a table vs moving entries to another table Thanks for your answer :) So I understand that partition will help me with the data storage for old records definitely, so should I make a partitioned table for inactive records and a table for active records as active records will not exceed the thousand mark or should I keep them in one partitioned table based on active inactive?? |
|
Sep 22 |
comment |
Partitioning a table vs moving entries to another table @Phil Its only that I need access to only some hundreds of the records which are active. Once the entry become inactive It will be needed only and only for reports and analysis, once in a month. And about volumes it will grow with time but active records will be limited to a few hundreds or thousand only. |
|
Sep 21 |
awarded | Student |
|
Sep 21 |
asked | Partitioning a table vs moving entries to another table |
