| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Comments:
<0> Hi, how to escape special characters, like ' in mysql statements? Is replacing ' with \' the best way ?
<1> i could neglect the thing :), it's only a small percentage
<1> :)
<2> lol
<2> no clue william, I usually use \
<2> but dunno if it's the best way
<2> !man SQL_BIG_SELECTS
<3> Nothing found.
<2> bah
<2> google it is then
<4> !man EXAMINE
<3> Nothing found.
<0> Kris, ah, i found it. there is a mysql_escape().
<2> ooooh cool :)
<2> !man SET
<3> (The SET Type) : http://dev.mysql.com/doc/mysql/en/SET.html
<2> !man SET Syntax
<3> (SET Syntax) : http://dev.mysql.com/doc/mysql/en/SET_OPTION.html
<2> ah ha!
<2> problem with using these bots to find things in the documentation is you have to know what you're looking for in the first place
<5> lol you could just read the manual :P
<2> from begining to end?
<2> o.O
<5> well why not be unique :P
<2> I'd be asleep for a decade :-/
<5> cos i'm sure noone else has :P
<2> lol
<2> Well, I googled my error, which brought me to the german mysql manual, which at least showed me what I needed to search for in the documentation
<2> once I had that it fixed my problem
<2> seems to be working now without errors and without mysterious lacks of data
<2> hehe
<5> :P
<2> now to comment out my debugging code and see if it still works when i show it to the client in the morning
<2> hehe
<5> another couple of queries like that and you'll be an old hand at joins :P
<2> lol
<2> I can hope
<2> it was a lot trickier than I thought it'd be at first
<5> it's a lot simpler than it looks though
<5> once you get used to thinking that way
<2> http://pastebin.com/630399
<2> there we go
<2> the final fixed version
<2> still feels kludgy to me
<2> but it looks elegant on the front end side
<2> and that's all anyone will care about
<5> often queries that have to do that sort of thing end up looking kludgy
<5> best thing to do is move on to the next one :P
<2> :)
<2> i'm just glad to have this one behind me ;)
<5> i usually like to format my sql as well :P
<2> how so?
<2> character returns and such?
<5> inside the $thisSQL
<5> yup
<5> well i tend to write web applications in perl
<2> yeah i was after quick and dirty
<5> so i can split strings over lines easily
<2> I used to use perl but php is so much faster for me to write in
<2> I still use it on occasion for back end stuff though
<5> heh i can code perl as fast as i can type
<2> hehe
<2> I used perl extensively from 1997 to 2001
<2> then I met php
<5> but if i know something can be done in sql i will figure out how to do it :P
<2> and never looked back
<5> i met php and glared and squinted at it and then went back to perl :P
<2> lol
<6> I'm so happy to forget perl
<6> ;-)
<2> I like php because it's an overly simplified version of perl
<5> lol
<5> that is precisely what i hated about it
<5> :P
<2> hehe
<2> only time i use perl now is when I encounter something that can't be done with php
<2> which doesn't happen often
<5> heh python is nice too
<2> biggest selling point for me actually is being able to embed stuff in html pages hehe
<6> at least you can have JIT compiler for it
<2> python has its plusses too hehe
<5> but i do enjoy the challenge of writing entire applications in sql :P
<2> lol
<7> but sql has no ui other than the table or rows and columns
<7> maybe stored procedure
<5> well the developers write the front end
<5> which is basically a form that calls stored procedures
<2> heh
<2> too bad i work for a graphic design firm
<2> to them a programmer is a programmer, no difference between front and back end
<5> well pretty much everything needs databases these days
<2> if i had my way i'd stick with the back end and let a designer make it pretty
<5> is the best way to do things
<8> Got error 134 when reading table './customer_028/Article' -- what gives?
<5> i have never got around to learning how to make things pretty
<5> so i just stick to coding and designing databases and interfaces
<6> !perror 134
<3> MySQL error: 134 = Record was already deleted (or record file crashed)
<8> humm
<8> when would that happen?
<2> :p
<5> lol
<2> I find that google is quite handy with error messages
<5> i find that google is quite handy for most things
<2> 9 times out of 10 it finds the answer before searching the mysql manual does
<7> error 134 can happend when you enable delay_key_write and kill the server before it can update the index
<7> a search found the index but has no record to read
<8> INSERT DELAYED into that is?
<5> should that be able to happen ? :S
<5> isn't the table locked ?
<7> if you kill it without letting it shutdown properly
<8> or is delay_key_write another setting?
<5> even if you do that it should still have safeguards :S
<8> well i never killed it... i did /etc/init.d/mysql restart -- does that kill?
<5> lol more than likely Bheam :P
<2> I'd say most definitely
<8> well wtf, how do i let it shutdown "properly" then :p
<6> Bheam: mysqladmin shutdown
<8> bah
<8> why doesn't the mysql start/stop script do that then?
<5> it is most likely a script produced by the maker of your distribution
<7> it should shutdown properly with the script
<8> k
<5> yup kill by itself usually sends a signal for the app to shut itself down
<8> well i read the script and it says 'kill'
<7> kill got different level
<8> anyway i'm not sure if that's what happened - but.. i never use INSERT DELAYED into the table in question, so i still dont' know why the error occured
<2> Well, I'm gonna call it a night, thanks for the help everyone!
<8> 060323 16:08:11 [ERROR] /usr/sbin/mysqld: Can't open file: 'Article.MYI' (errno: 145)
<8> 060324 3:03:32 [ERROR] /usr/sbin/mysqld: Can't find file: 'days.MYI' (errno: 2)
<8> what's the difference?
<8> i mean except the obvious :p
<8> !perror 145
<3> MySQL error: 145 = Table was marked as crashed and should be repaired
<8> !perror 2
<3> System error: 2 = No such file or directory
<8> well i sure question how the file can just disappear
<8> is there any option to make mysql autorepair tables?
<7> deleted
<8> well why would mysql delete the index file?
<8> i sure as hell didn't :p
<7> Bheam: there is some option for auto recover
<7> Bheam: it should not delete the index file
Return to
#mysql
or
Go to some related
logs:
guide to charsets
ReiserFS zam-7001 fix
hdparam apt-get
building Xorg 7
bash: /usr/bin/who: Input/output error
a problem GNOME_MixerApplet emerge
#css
Can't locate Algorithm GenerateSequence.pm
#lisp
rsync syntax error near unexpected token `newline'
|
|