Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 3 13
Impact
~30k people reached

  • 0 posts edited
  • 1 helpful flag
  • 13 votes cast
Mar
24
awarded  Notable Question
Mar
12
comment MySQL - Group By - How does it determine which row to return from joined table
@Phil: That's sort of what we figured too, that under the hood MySQL was picking the correct row for performance reasons, which may be directed by indices or some other outlyer.
Mar
12
revised MySQL - Group By - How does it determine which row to return from joined table
edited body
Mar
11
asked MySQL - Group By - How does it determine which row to return from joined table
Feb
6
awarded  Popular Question
Feb
3
awarded  Famous Question
Jan
16
comment MySQL 5.1: change datadir variable value in my.cnf
Terrible suggestion. Figure out the permissions problem rather than weakening your security.
Dec
19
accepted SELECT INTO OUTFILE vs INSERT INTO … SELECT
Dec
19
comment SELECT INTO OUTFILE vs INSERT INTO … SELECT
Thx for the in-depth answer!
Dec
15
comment SELECT INTO OUTFILE vs INSERT INTO … SELECT
I wasn't notified that you updated your answer, so I did bounty assuming it wasn't. Your explanation does make sense, in theory, however I am looking for a more authoritative response, in hopes that the overhead of the separate file (as you correctly mentioned) may be worth the trade-off in complexity for improved performance.
Dec
10
comment SELECT INTO OUTFILE vs INSERT INTO … SELECT
Correct I understand the results of the each command, what I am wondering, at the db layer, if there is a performance bonus using one over the other? I'd always thought that derived tables are never a good solution, but wanted to know why, within this context.
Dec
10
comment SELECT INTO OUTFILE vs INSERT INTO … SELECT
Thx for the answer, and it does help, but the main point of the OP was to determine if there is a benefit for using SELECT INTO OUTFILE over INSERT INTO ... SELECT?
Dec
10
asked SELECT INTO OUTFILE vs INSERT INTO … SELECT
Dec
2
accepted HA - MySQL Master Master replication - Duplicate entry errors
Dec
2
comment HA - MySQL Master Master replication - Duplicate entry errors
I'll take a look, thx.
Oct
21
comment HA - MySQL Master Master replication - Duplicate entry errors
I've actually seen single write master-master replication work in environments serving 200+ million hits per month. Perhaps it's not the ideal solution (still subjective imo), but at this juncture, I have no other alternative. As we are bootstrapping, we are lucky to even have this level of fault tolerance. +1 for the suggestions tho.
Oct
19
asked HA - MySQL Master Master replication - Duplicate entry errors
Aug
15
comment MySQL Replication - Master Master - Single Master write
Doh, already puppetized those changes :( . Ok I'll back out. Rather just replicate all databases in case new ones are added in the future, without having to add to a puppet config, and re-run puppet on masters. Thanks again.
Aug
15
revised MySQL Replication - Master Master - Single Master write
added 2 characters in body
Aug
15
accepted MySQL Replication - Master Master - Single Master write