#mysql
30 October 2007
Total 22 pages. You are browsing page 2/22.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last
00:52 <****> ironpig: I am no longer sure, after doing some googling.
00:52 <****> Shai_Tan can you re-design the data structure?
00:52 <****> bz029: yes
00:53 <****> then do so - all things to be identified by one ID have to go in one table; if these things are not all of the same type then add a type column and a type table
00:53 <****> Shai_Tan you have different ways to do it then
00:53 <****> adaptr: thats fine, but how to SELECT * FROM @type WHERE id=3
00:53 <****> the rest belongs in the application, not SQL
00:53 <****> Shai_Tan no, that's obviously not it
00:53 <****> ironpig: I was wrong.
00:53 <****> Shai_Tan that's what JOINs are for
00:54 <****> I would stlli need to store the table name
00:54 <****> ironpig: set 'bind-address=' to the ip address of the nic you want it to listen on for tcp connections.
00:54 <****> Shai_Tan: No no
00:55 <****> Presumably, when you populate the feature table, you know what you're putting in there
00:55 <****> A.. type!
00:55 <****> um, yah... I thought something was wrong... the firewall is blocking this port :(
00:55 <****> sensei: ok, so type is "event"
00:55 <****> ironpig: bind-address, firewall, and mysql user grant privileges.
00:55 <****> I store event_id and event
00:56 <****> type would be product or article.. personally I'd look into merging those tables (keeping what I said above in mind :) )
00:56 <****> ironpig: the default mysqld port is 3306.
00:56 <****> Shai_Tan it's hard to see what the data represents, and if it's hard to see that usually means it's not that well designed
00:57 <****> yah, but I like to do everything on different number ports. It helps me see the real security threats.
00:57 <****> huh ?
00:57 <****> how would running services on non-standard ports make you *see* security *threats* ?
00:57 <****> he must be daydreaming
00:57 <****> crack
00:57 <****> the log files
00:57 <****> it might make you see security *breaches* easier - but that's already too late
00:58 <****> you don't *see* security threats - you protect against them
00:58 <****> you don't look at your log files?
00:58 <****> for what purpose ?
00:58 <****> ironpig: changing the port from the default value does not make you more secure.
00:58 <****> I never said that.
00:59 <****> it make the log file easier to read.
00:59 <****> how so?
00:59 <****> squash 'im, thumbs ;)
01:00 <****> That's the spirit... erm, wait
01:00 <****> :)
01:00 <****> if someone is trying to connect with one of those kiddy scripts that just try typical login and passwords over and over again, the log file gets pretty long.
01:00 * thumbs smashes ironpig
01:01 <****> ironpig: Seriously, you don't stop kiddie scripts at database level
01:01 <****> ironpig a better determent against that would be to block the offending IP after 3 or so tries
01:01 <****> also ^^ yes
01:02 <****> what if the IP is from someones computer on the internal network?
01:02 <****> somethign like snort can help you identify IPs that try to hacbreak in - and block them ASAP
01:02 <****> Nothing says you need to allow anything in just because you happen to share a network
01:02 <****> ironpig then you ... kill them, but politely, as they are your colleagues
01:02 <****> lol
01:03 <****> or one of my colleagues has something nasty on their system.
01:03 <****> Sysadmins around the world appreciate your concern for security, but start at the other end and work your way downwards ;)
01:03 <****> then they'll be thankful that you alerted them to a possible security breach which could get them fired for surfing pr0n.. or you MAKE them thankful :)
01:04 <****> heh
01:04 <****> Much like you DBAN the pc's of colleagues who leaves them unlocked
01:06 <****> well, most of what I'm doing here is for the internal network... The public IP reference I made was me trying to test the thing. I thought that the firewall had a different set up for the two network cards, but I was wrong.
01:07 <****> dangerous assumptions at the best of times
01:07 <****> its best to test :)
01:07 <****> Said Adolf and gave Poland a go..
01:07 <****> the best thing you can do for your server is to A remove any and all wildcarded hosts from your grant tables, for every user who has more than USAGE rights, and
01:08 <****> Worst analogy today \o/
01:08 <****> B add rights as they are *required*, and no more
01:09 <****> I agree, I figured that setting up the server to listen to only traffic coming from internal traffic might help.
01:09 <****> sensei++
01:11 <****> ironpig if your machine is behid a decent firewall, as it should be, then that's not really the biggest issue
01:11 <****> *valid* user abuse or misuse is much more likely
01:12 <****> well, see I didn't set up the "main" firewall, so I don't really trust it. But its a nice firewall. I'm not sure the monkey setting it up has any idea what hes doing.
01:12 <****> I also have a firewall on this server.
01:12 <****> but its just pf.
01:12 <****> *ahem*
01:13 <****> just pf.... pf is great as far as firewalls go
01:13 <****> if you know what your doing... I can do some basic stuff with pf but I'm not a pro.
01:14 <****> is there a good resource that explains how mysql works -- like I know all the syntax and everything, but I don't know how its actually doing everything
01:15 <****> didn't you say that before?
01:15 <****> yes
01:15 <****> I didn't get an answer
01:15 <****> so I figured I'd ask again an hour later
01:16 <****> ok, ask in another hour then
01:16 <****> k
01:23 <****> so I have a table with 11 million records
01:24 <****> what is thebset way to make queries faster
01:24 <****> make 26 tables for each first letter of their last name?
01:25 <****> indexes being the obvious answer, but otherwise partitioning the table in that manner might be an idea, depends on how you use it really
01:26 <****> ah
01:28 <****> putting data in the table name is a nono
01:28 <****> nono means no no
01:28 <****> partition the table makes it fast when you search by the col used to partition, but when doing other col search it will need to search multiple tables
01:29 <****> what do you mean chad
01:29 <****> Might be noteworthy that inserting data suffers a tad as well
01:29 <****> tators: you want to know the internal? the source code is the final documentation
01:30 <****> kinseong: more like a working knowledge, I won't be able to understand the source code
01:30 <****> but I'd like it paraphrased in english per se
01:30 <****> !man indexing
01:30 <****> (Column Indexes) : http://dev.mysql.com/doc/mysql/en/indexes.html
01:31 <****> y would anyone install a 32 bit binary package and a 64 bit server of mysql. Sorry I am a newbie so I got to ask
01:32 <****> archangel7863: If you've got 32 bit third party closed source applications which relies on 32 bit components, it might be necessary
01:32 <****> *chosing the best examples*
01:33 <****> is hashmysql down
01:33 <****> what is the 64 bit server for then?
01:35 <****> also, is there a working definition of indexes
01:35 <****> the dev.mysql assumes you know what it is
Total 22 pages. You are browsing page 2/22.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last