#mysql
15 November 2007
Total 10 pages. You are browsing page 1/10.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last
--- Log opened Thu Nov 15 00:00:06 2007
--- Day changed Thu Nov 15 2007
00:00 <****> oh, sorry, I mean about half are a single row with an index
00:00 <****> The rest are multiple rows
00:00 <****> that's like asking "Can my car go zero to 60 in 10 seconds" To someone that has no idea what kind of car you have and has never seen it
00:00 <****> Oh, just a minute
00:00 <****> I'm looking at what the server has
00:00 <****> just benchmark it and find out
00:00 <****> Xgc, Adaptr: I was double wrong: it is *some* Bs.
00:01 <****> you maybe have a mustang but it may also be trying to pull a trailer full of dead hookers
00:01 <****> we don't know
00:01 <****> Xgc, Adaptr: I'm not gonna get you guys into that again; I'm just clarifying
00:01 <****> ebergen: woud that be different from live hookers?
00:01 * arjenAU has not tried either, but is looking to ebergen for expertise
00:02 <****> I would imagine live hookers move around a bit more thus making the trailer harder to control
00:02 <****> now, that's a good sentence to log in to
00:02 <****> so a trailer of dead hookers offers more precise measurements ?
00:02 <****> dead hookers are, pardon the pun, dead weight :)
00:02 <****> although it could be argued that live ones offer a better real-world load
00:03 <****> hey... if i have a master/slave configuration, how do i know when the slave is updated regarding the master? Is there some cmd I can run from the mysql promt/api that can giveme this information?
00:03 <****> and does it matter that they're hookers, or would enother occupation do?
00:03 <****> show status ?
00:03 <****> sv2_: show slave status\G
00:03 <****> arjenAU I suppose ebergen knows his hookers
00:03 <****> adaptr: he doesnt have a mustang tho
00:03 <****> you go with what you know, after all
00:03 <****> I don't
00:04 <****> my truck would have no problem hauling a trailer of dead hookers
00:04 <****> no but that's the beauty of benchmarking, see - if you've done a trailer behind a pinto, you can compare :)
00:04 <****> ebergen: just pimps his mysql expertise ;-)
00:04 <****> hahaha
00:04 <****> adaptr: he doesn't have apinto either. if only.
00:04 <****> it'd have to be a small trailer, then
00:04 <****> he has some offensively large truck thing
00:04 <****> my truck: http://flickr.com/photos/35653522@N00/1263931852/
00:04 <****> that would go well with the offensively live hookers
00:05 <****> are you the scary dude or the lobster nerd ?
00:05 <****> that's one bigass lobster
00:06 <****> adaptr: Would MySQL (or pretty much any other database) probably choke when using a Pentium III for that number of queries?
00:06 <****> lobster nerd :)
00:06 <****> ebergen: Nice party
00:06 <****> pingveno it. all. DEPENDS!
00:06 <****> ebergen nice hookers :)
00:06 <****> depends on what?
00:06 <****> see, he has teh expertise
00:06 <****> that lobster was 15lbs
00:06 <****> pingveno everything!
00:06 <****> ebergen I know - the caption says so...
00:06 <****> obviosity++
00:06 <****> pingveno: everything.
00:06 <****> yeah forgot about that
00:07 <****> Is there any website where I could look at everything?
00:07 <****> I have a weird issue... I'm getting an error saying that 'DBD::mysql::st execute failed: Duplicate entry '4294967295' for key 1' however it's an auto increment primary key and no value is being specified...
00:07 <****> pingveno if you had a read-only database that fit into the 4GB ram you could run it entirely on a pentium-200
00:07 <****> that lobster creeped me out when I picked it upt
00:07 <****> the picture creeps me out
00:07 <****> so yeah
00:07 <****> I expected it to be sort of stiff but the joins were really fluid
00:07 <****> it was dead, I hope
00:07 <****> kritical: you maxed it out on an INT UNSIGNED. you must've inserted something specific earlier.
00:07 <****> or you'd be minus some typing fingers now
00:08 <****> yes it was dead
00:08 <****> it died earlier that day
00:08 <****> arjenAU, sorry I don't understand...
00:08 <****> adaptr: Ah, I see. I'll take another look at the server. I'm not actually sure which server it will be, though...
00:08 <****> kritical: remove offending rowid and alter table auto_increment=# to set it back to asnity, or changecol type to bigint
00:08 <****> we had to cut it into pieces to cook it because none of us owned a large enough pot
00:08 <****> kritical: check your table data, there'll be a row there with that value. and as auto-inc only goes up.... it's the highest # allowed for the int unsigned col type. so you're effectively out of numbers in this context
00:09 <****> arjenAU, I understand that... but I was under the assumption it would just start from the start again?...
00:09 <****> kritical: that'd be dangerous
00:10 <****> kritical: and the manual says otherwise also, so assumption wrong.
00:10 <****> kritical: you can change to bigint unsgned it you want.
00:10 <****> arjenAU, you know what they say about assumptions ;)
00:10 <****> kritical: I wouldn't presume to know
00:10 <****> having to deal with mssql for the last few weeks i've come to really appreciate mysql
00:11 <****> really ?
00:11 <****> really
00:11 <****> what's better in mysql, then ?
00:11 <****> syntax is far richer and easier to write
00:11 <****> I just use MS SQL for serious work, so I have no experience using mySQL for "real" data
00:11 <****> arjenAU, thanks, greatly appreciated!
00:11 <****> mysql has better datatypes
00:11 <****> Abobo then you can't have used 2005...
00:12 <****> adaptr, correct
00:12 <****> how can datatypes be "better" ?
00:12 <****> adaptr, because mysql has enum set etc
00:12 <****> Abobo SQL2000 is indeed the bastard son of DBASE 3
00:12 <****> but 2005 is a whole nother kettle of lobster
00:12 <****> yea well who cares
00:12 <****> hi. i installed php them mysql. and now mysql doesn't come up in phpinfo(). which one should be installed first?
00:12 <****> i dont have 20 thousand dollars to spend
00:12 <****> it's a complete rewrite, and you'd be hard pressed to find anything in mysql that it doesn't do as well or better
00:12 <****> we already did :)
00:13 <****> so it's a win/win for me
00:13 <****> slimjimflim you just answered your own question, dint ya ?
00:13 <****> ok then, whats better in mssql2000, disregarding the crapity crap like triggers and stored procedures
00:13 <****> er 2005
00:13 <****> i hoped so
00:13 <****> thanks for confirming that tho
00:13 <****> adaptr: you don't want to bet on such things. you lose.
Total 10 pages. You are browsing page 1/10.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last