MySQL can blow me
Sep. 26th, 2006 06:54 pmI have gotten like 4 really fucked up MySQL cases today and I'm completely burnt out. If I have to stare at the MySQL command line one more time I'm going to fucking explode.
X-Posted to my journal
mysql --user=kaytie --password=daddysgirl kaytie mysql> show variables like "patience"; Empty set (0.00 sec) mysql> help There is no help for you, may we try the following options? drink (\d) Sets drink query delimiter to TRUE ego (\e) Inflates ego (currently disabled) home (\h) Attempts to go home, unable to leave at this time quit (\q) If only you could... rehash (\#) Reinvent the wheel? For additional help, type 'sepakku'
X-Posted to my journal
no subject
Date: 2006-09-26 11:07 pm (UTC)truncate table events
Eventually I'll get in trouble for this. But I haven't yet.
no subject
Date: 2006-09-27 12:27 am (UTC)Even the one that had a bunch of mission critical crap that I used for my job that the boss forced me to kill off because I was hosting it at home instead of on a crappy work machine, and because it ran on a unix platform instead of M$.
no subject
Date: 2006-09-27 02:44 am (UTC)mysql> show variables like "%patience%";
however, I share your pain. mysql is breaindead in so many ways it's not funny.
no subject
Date: 2006-09-27 03:09 am (UTC)mysql> show variables like "tmpdir";
it will output something like
adding the "%" sign will should be used if there's an assigned variable or table name, or if it's being run via a shell script... at least that's my experience with it.
^.^
no subject
Date: 2006-09-27 12:53 pm (UTC)no subject
Date: 2006-09-28 07:55 am (UTC)no subject
Date: 2006-10-26 04:47 pm (UTC)