Lucid, the actual.

Alarie: If it’s just a straight comparison debian/centos I will do that though

Knudsuig: What are you talking about? it’s a file on the filesystem

Magness: You must be fun at parties.

Mannina: Lots of times distros do things differently

Cork: Apache for example, distros split different things different ways

Hoffine: My original question was exactly what you’re beating me up over right now

Aden: The answer is yes, there is cli-way to view a file.

Coombes: And everything I found on google was about installing and upgrading, not about comparing configs or any way of getting succinct configuration information

Plover: I know about CLI tools

Baldwyn: I’m talking about googling the location of my.cnf if you can’t find it in the usual location

Raymond: I can use cat and vim, diff, etc. that’s fine and it wasn’t what I said the problem was

Langford: Oh, look at that. first result:

Kalima: I was actually worried about a bunch of includes and things that radically alter config

Fasciano: I can find my.cnf without google

Nogueda: I’ll wait 5 hours for someone who isn’t p***ive aggressive or with some kind of agenda for conflict

Agney: Oh i thought you meant distros have different ways of dividing config files. if you meant dividing arguments inside the file, they’re should be the same if not similar and would depend on what flavour of mysql, mysql version etc

Crady: Yeah I was worried that in trying to compare them

Phippin: Debian will have 30 different one-line cnf files that make it impossible to achieve

Riefer: Ok i will stop helping you

Laduc: So you run mysql –get-config or whatever and compare those outputs

Mcmahan: Lucid: or pt-config-diff from percona toolkit like i said earlier

Depriest: Danblack: thanks, will check it out

Kellar: Web/irccloud caught fire :-

Bingham: Somebody got the kline wrong :

Swed: Lucid, can you do “****yze table name;” and start with the one from your paste – then re-check the cardinality column if it changed much

Bauder: Swed: ah okay. I did make index changes so that sounds like it’d make sense

Rudin: Swed: definitely changed significantly but still slow

Swed: Lucid, is it innodb? stats may be computed at different times and it may depend on some configs too

Swed: Lucid, did it get closer to the fast variant? did explain change too?

Parshall: Swed: yeah its innodb

Hasberry: Swed:

Makela: Noob question on table design: if i query the amount of fruit in a fruit shop, at 5pm perhaps they’ll have 5 apples, 3 oranges, 1 banana. if i wanted to graph this data over time, could i create a table with fields “timestamp, fruitType, fruitQuantity” and add a row for every fruit every time i query the fruit quantities? then when i want to graph, i just get all rows matching a particular timestamp. or is this bad design?

Qualle: Swed: speed of the query doesn’t seem to have changed

Swed: Lucid, it actually went even farther from the numbers shown for “HAPPY”.

Saras: Hey guys , i have a query to select empty rooms between two date in hotel but empty room condition is not working

Greider: AND room_kind_hotel_capacity.capacity 0 , the query shows all the room , how can i correct it ?

Fluck: Swed: well there is 1 extra day of data in there 10k ranks, probably close to 0 sellers but this is maybe like 1%-2% of the overall data

Heltsley: Swed: I can make the data identical if you’d like

Keil: It really seems like something didn’t change on the 2nd machine when I changed the indexes though

Swed: Lucid, the actual difference between the plans seems to be the usage of index “SellerName” which seems to cover a varchar field – do you compare the actual varchar value in the query?