@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18



Comments:

<0> is there anything I need to do to make it so mysql can accept connections from other pc's?
<1> no
<1> riddlebox, What error do you get?
<2> It's very likely that I want to use the primary key in either ASC or DESC...
<1> God created a language for a reason. So you can tell it what you want and so it doesn't have to guess.
<0> _mysql_exceptions.OperationalError: (2003, "Can't connect to MySQL server on '192.168.0.100' (111)")
<3> will: i'd say the languages god created through linguistic evolution do a particularly bad job of that :)
<1> :P
<3> human language is filled with senseless ambiguity
<1> riddlebox, Check my.cnf for skipn-networking or bind-address
<1> Comment those out.
<2> OK. Basically, I have no idea what to do now.
<1> GROUP BY
<4> KimmoA: Try using GROUP BY.
<2> I'm looking at http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html
<4> KimmoA: MySQL has a little feature that you might enjoy.



<1> Did anyone tell you that SELECT * is bad?? :)
<4> KimmoA: SELECT * FROM table1 GROUP BY yourField;
<2> will: Yes.
<4> KimmoA: The SQL standard doesn't allow this.
<2> will: And I tell them that I use them all...
<2> Xgc: HMM...
<4> KimmoA: But MySQL does.
<1> KimmoA, Save youself time NOW by doing it the "long" way
<2> (Whys is it bad? Is it that much of a overhead?)
<2> s/ a / an /
<1> !tell us about evil
<5> will asked me to tell you this: Evil is clearly defined at http://www.parseerror.com/sql/select*isevil.html
<1> Is one reason. The main reason is what Xgc pointed out.
<0> will, can I do some sort of restart now to start using the networking?
<1> riddlebox, What did you do?
<1> Yes, shutdown the server and restart it.
<0> commented out skip-networking
<1> Like any other service
<2> This is off topic, but the latest version of MySQL Query Browser (at least the one I got the last time) seems to make marked text's background AND foreground white. Kind of annoying.
<0> thanks will
<1> np
<2> OK, so that worked.
<2> Now I'm scared.
<2> How the hell could that work?
<2> First, even though I'm likely never gonna switch database, I don't like using non-standard stuff...
<4> KimmoA: Magic.
<2> But even apart from that, is truely feels like magic.
<2> I admit that I'm a bit (cough!) rusty, but it feels to me that "GROUP BY" isn't the most logical keyword(s) to use.
<4> KimmoA: It's not supposed to work for the same reason selecting non-agggregates of a GROUP is normally invalid.
<1> Actually, you probably did not get it to work. Recheck your data.
<2> You have a point there...
<4> KimmoA: When using GROUP BY, you're supposed to select aggregates (SUM, AVG, COUNT, along with fields specified in the GROUP BY list).
<1> Unless you've been reading up a lot more docs than I ***ume.
<2> It doesn't seem to be working in the real application...
<6> I love you will
<1> I hate you groundup
<6> At least you have feelings towards me
<4> KimmoA: When you attempt to select non-aggregates of a group, the engine has to arbitrarily pick one of the available values from the rows of the group.
<1> true
<2> Hrm...
<4> KimmoA: That's why the SQL specification doesn't allow this. Some engines offer other more complex aggregation and windowing mechanisms for use within groups.
<2> Maybe I should state my question again, clearer: "I want to return rows as normal, but only "the latest" of such with identical "title" and identical "source". The "latest" is decided using the "id" column."
<4> These are extensions to the spec.
<4> KimmoA: That can be done, but not with a simple DISTINCT or simple GROUP BY.
<2> I see. :(
<2> I remember trying to remove duplicate posts from my database.
<2> I never was able to.
<4> KimmoA: http://dev.mysql.com/doc/refman/5.0/en/example-maximum-column-group-row.html
<4> KimmoA: Read the user comments as well.
<7> hmm, could I get some ***istance with a MySQL problem please?
<4> KimmoA: In your case you may need to JOIN the table against itself.
<2> It seems to me that overly complicated queries often are a result of bad design...
<2> Or at least too complex design.
<4> KimmoA: In this case, the solution is simple. What you call the simple solution has undefined behavior.
<7> I am trying to reset my root p***word using the method described in the documentation, but when I run the sql query from in MySQL, it shows affected rows: 0, etc
<7> mysql> UPDATE mysql.user SET P***word=P***WORD('p***word') WHERE User='root';
<7> Query OK, 0 rows affected (0.01 sec)
<7> Rows matched: 0 Changed: 0 Warnings: 0
<2> Xgc: "What you call the simple solution has undefined behavior." <-- What is that supposed to mean?
<4> KimmoA: Your idea of the simple solution: SELECT DISTINCT ... FROM table1; has undefined behavior. The result can't be determined by the specification.
<4> KimmoA: Sorry. I mean, it can't do what you want.



<7> anyone care to help me ?
<2> Xgc: Yeah. I know. I just told you what I had... :/
<4> KimmoA: The GROUP BY form has undefined behavior and is rejected by any compiant engine.
<4> KimmoA: The real solution is not complex. I'm not sure why you think it is.
<2> HelpMe: Why do you use "P***word" instead of "p***word" and "User" instead of "user"? I don't remember if that matters, but I always do stuff case-sensitive.
<2> Xgc: Hmm...
<2> Xgc: Well... I think so because I don't know how to do it, basically... ;)
<4> KimmoA: Ok. That's understandable. Usually, that feeling subsides eventually.
<2> Also, what are your thoughts on "`foobar`" VS "foobar"?
<4> KimmoA: Its mispelled.
<2> I have a field called "e-mail", which makes me have to use `e-mail` instead of "e-mail".
<4> KimmoA: The proper term is fubar.
<2> But otherwise, I always don't quote it.
<2> Roar...
<2> Like "SELECT user..." instead of "SELECT `user`...".
<4> KimmoA: I don't like unnecessary backtics. It makes the SQL tough to read.
<2> I don't know if that's as bad as doing "<label for=user>" instead of "<label for="user">" in HTML...
<2> Yeah. I agree.
<1> HelpMe, SELECT * FROM mysql.user WHERE User = 'root';
<7> empty set
<4> HelpMe :)
<1> Why did you delete your root user? :)
<7> I didn't
<7> I just recently had plesk installed
<7> and uninstalled it and all this started happening
<7> if I delete the database files and uninstall mysql and reinstall it will it fix it ?
<4> HelpMe: Yes. You don't need to do that. But you can.
<7> What can I do to fix it ?
<7> Just add the user back in ?
<4> HelpMe: You could simply follow the --skip-grant-tables mechanism and add a new root user.
<7> im still in that
<4> Then just add the user.
<7> looking up the command right now to add the root user in again
<2> Well... see you later.
<7> there, I got it.
<7> Thanks alot, guys
<8> arjenAU: Can you recommend a site that shows good examples of setting up indexes
<8> I'm trying to setup an index where I have auto parts listed by part name, and have them reference different components that they are part of.
<9> UncleD: oh dear. it's actually common sense. or a skill that you need to learn. a cookbook for it makes no sense.
<8> So if autopart A is found in components: Transmission, Manifold, etc.
<9> Woosta: crunch?
<8> Then A points to Transmission, Manifold, etc
<8> Well, I understand the concept :)
<8> arjenAU: I guess you don't have any example sites then.
<8> Ill dig something up I guess :)
<9> partlists... something that SQL for Smarties (book) might cover. has little to do with indexes
<9> it has everything to do with table design
<8> you're not understanding my situation though
<9> and whose prob is that? ;-)
<8> I understand the design of tables is important.
<10> How do I do the auto increment thing to a field in MySQL
<8> AUTO_INCREMENT
<11> pilgrim: check the mysql.com site for create table syntax
<10> Woosta, got it. it's auto_increment
<12> I need some help
<12> I'm needing to store a 128 bit hexidecimal number in mysql
<12> whats my best choice as a datatype
<1> What are your choices?
<13> I'd say varchar?
<12> ok
<14> maybe char
<1> TINYTEXT
<11> I'd either go an int or a char .. convert it on the way out
<11> but that's me :)
<13> int won't take hex
<3> don't use varchar or tinytext
<3> you don't store it in hex representation, that'd be even crazier
<13> why not?
<12> well, all I know is I need to use something, it's a md5 checksum it's storing
<13> yeah, converting it to an int is silly
<13> what is tinytext?
<12> well, I'm pulling it out in hex


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #mysql
or
Go to some related logs:

#lisp
#perl
error opening security policy file ubuntu
read-only filesystem + ntfs + ubuntu
#perl
#debian
gentoo booting hangs coldplugging
treetagger gentoo
ignasoft
#perl



Home  |  disclaimer  |  contact  |  submit quotes