203 reputation
19
bio website
location Cluj-Napoca, Romania
age
visits member for 2 years, 3 months
seen 18 hours ago

I work as a PHP developer at Pentalog where we develop the largest dating site in Europe.

I thrive in challenging environments and am never afraid to get my hands dirty.

My passions include computer programming, psychology and poker.


Jun
4
awarded  Yearling
Dec
3
comment Change MySQL 4.1 Windos to MySQL 4.1 Linux- Problem with the key Sensitive in query
OMG it's 2004. I should buy some Apple shares.
Sep
6
comment How to update a table from a another table
Sorry, I guess I was too pissed off to realize I was out of line. I'll delete it.
Jun
13
awarded  Popular Question
May
21
awarded  Caucus
Feb
20
awarded  Commentator
Feb
20
comment Mysql: disable unused schemas
Actually, if you have many databases, starting MySQL will not automatically put them in RAM... unless you explicitly set something like that up... which clearly you didn't... Have a look at MySQL configuration, maybe the cache sizes for InnoDB are too high or... something similar
Jul
25
awarded  Teacher
Jul
25
comment Why is DELETE so much slower than SELECT, then DELETE by id?
@itsadok I wrote it as an answer :) .
Jul
25
answered Why is DELETE so much slower than SELECT, then DELETE by id?
Jul
25
comment Why is DELETE so much slower than SELECT, then DELETE by id?
@pconcepcion if you write EXPLAIN DELETE FROM...., it won't work. From what I know, it works only on SELECTs.
Jul
25
comment Why is DELETE so much slower than SELECT, then DELETE by id?
Yeah but.... you were right in the first place. If the field email is unindexed, then both DELETE and SELECT should work equally slow. Or: You say that the table is queried heavily. Maybe when you tried your first DELETE there was someone else running a really long transaction on those rows...
Jul
25
comment Why is DELETE so much slower than SELECT, then DELETE by id?
I guess you absolutely must post a SHOW CREATE TABLE and probably an EXPLAIN... too.
Jul
23
awarded  Citizen Patrol
Jul
23
awarded  Critic
May
17
awarded  Scholar
May
17
accepted Why doesn't InnoDB store the row count?
May
16
comment Why doesn't InnoDB store the row count?
Sounds very good (+1), you certainly made me curious about that option. If I ever get my hands on a table large enough to test this (let's say > 100K rows), I will definitely try it.
May
16
comment Why doesn't InnoDB store the row count?
@Remus I totall forgot about the SHOW TABLE STATUS. There is actually a row count there, I wonder how it's maintained (will look it up). I gave you a +1 , but I'll wait for other answers before accepting. Thank you.
May
16
comment Why doesn't InnoDB store the row count?
Such informations are quite useful. Think about a website that has to display to its admins the number of users registered, the number of users banned, the number of posts/topics (if it contains a forum) etc. Doing COUNT(*) makes sense in this case. True, you can store in a table named "statistics" or something similar, but wouldn't it be easier to avoid something like that ?