Danblack: do***entation.

Decoux: Why are you using grants based on hostnames?

Nager: Because I prefer hostnames instead of IPs.

Goetze: Should still use CIDR.

Stipetich: And I don’t want to use %, as it’s in opened network.

Rosemore: Even more reason to use an IP. :

Harlston: Decoux: because name servers are easier to remember and usually don’t change.

Japp: IPs are harded to remember and might get changed :-

Maclin: I would hope if you’re running something in production IP’s aren’t changing!

Pulvermacher: Anyway, guys, I know there are dozens ways to fix it.

Axe: But I want to understand why it’s working that way.

Casamento: I want to understand that anomaly :-

Kjos: So the first problem here is it could be an issue outside MySQL, start with granting IP’s and go from tehre

Winge: Chucky_z: already did that, it works.

Brull: I addedd also grant with client.domain.com – still works.

Doe: On one server it works. On second one it doesn’t.

Doolittle: It doesn’t use IPs at all.

Desmeules: I mean, okay, it does, it resolves it.

Coltrin: But I don’t know what you want me to check :-

Hitchingham: It resolved it same way on both servers.

Hopwood: On server2 it doesn’t matter if grant is for ‘client’, or ‘client.domain.com’ – it works both ways.

Zebley: On server1 grant needs to be for ‘client.domain.com’, otherwise it doesn’t work.

Guedjian: Nsswitch is set to files,dns on all three servers.

Bartman: And /etc/hosts looks exactly same on all three servers.

Pressly: I have a table called material type with all the material types, id and description, I have another table that contains a foreing key to that material type id. I would like to create a view in where I can see only the description by joining those two tables

Bachinski: Pressly: you can select any columns you like from the join

Pressly: What kind of joind would that work?

Bachinski: Pressly: select t2 from t1 leftrightinner join t2 on t1.id=t2.id.

Lauby: Pressly: Any join would work fine. Try them all. See which one you like the best.

Bachinski: Pressly: select t2.column_name from t1 leftrightinner join t2 on t1.id=t2.id.

Harootunian: Pressly: You can even cross join them.

Vanaken: Pressly: Joins are like Venn diagrams! http://www.codeproject.com/KB/database/Visual_SQL_Joins.aspx

Coppock: I have two mysql servers in a master/slave setup. I didn’t set them up to begin with. The slave “show slave status” is giving me: “Could not find first log file name in binary log index file”. It looks like they’ve been out of sync for too long and the master has deleted the log for the slave to use

Miene: What’s the easiest way to get the slave caught up and working again?

Swarts: Is this the best way? http://stackoverflow.com/questions/2366018/how-to-re-sync-the-mysql-db-if-master-and-slave-have-different-database-incase-o

Shenkman: MTeck: there’s a percona tool that does this

Gonzaliz: That method works just fine i’ve used it in the past

Okada: MTeck: honestly – start from scratch.

Falvo: MTeck: See http://dev.mysql.com/doc/refman/5.6/en/replication-solutions.html

Bilby: Avoid the heresay of blogs, stackoverflow etc. refer to the offical docs.

Odum: Hello all. for clarification expire_log_days works to automatically remove bin and relay logs correct?

Thanos: Chucky_z: while pt-table-sync works if there are chunks in replication and statements that don’t replication it won’t help. easier just to start from scratch

Farlin: Pycoderf: ask the do***entation tells you.

Bourff: MTeck: depends on the method. start reading – there are a few options.

Eggleston: Danblack: do***entation says expire_log_days is for binlogs