| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Comments:
<0> dejx, for?
<0> dejx, /etc/init.d/mysql start
<1> /etc/....mysql start
<2> cappiz: the text/blob things are generally for big quantities of data
<1> thanks.
<2> tinytext may be an anomaly, but it probably doesn't behave how you want (and as you can see, it isn't) so use varchar
<1> root@notebook:~# mysql --socket=/var/run/mysqld/mysqld.sock -u root -p
<1> Enter p***word:
<1> Welcome to the MySQL monitor. Commands end with ; or \g.
<1> ooooooooooook, i'm in
<1> .
<0> dejx, so the sock file is just in the wrong place
<3> the thing osfameron is that my name can be more than 255 chars... there is actually no limit :
<2> cappiz: sure
<3> so then i should use tinytext?
<3> :P
<2> cappiz: but you might want to index on something else
<2> maybe an auto_increment primary key unless you were teached that that was a bad thing
<3> hehe... why bother to store extra info ?
<2> cappiz: are you asking a question or do you already know the answer?
<3> wel... my db needs to be very fast... and wouldnt it sink the speed of it by storeing a key that isnt really needed ?
<4> you'll sink it much faster by indexing the *wrong* data
<2> integers are nice
<3> hehe... name is the primasry info that i need do query based on
<2> computers like integers (actually they like binary)
<1> ERROR 1046 (3D000): No database selected
<3> osfameron could i priv msg you ?
<0> dejx, CREATE DATABASE name
<0> dejx, USE database_name
<1> USE ?
<1> http://pastebin.com/625791
<1> i have this
<5> dejx, http://tyson.homeunix.org/notes/mysql.html
<1> thanks beebum, i'll read
<0> cdjx yeah you need to create a databse to store your tables i
<6> what database use google ??? mysql, postgresql, oracle ?
<5> dejx, this will help too: http://dev.mysql.com/doc/refman/5.0/en/database-use.html
<7> Question: I'm currently using LOAD DATA LOCAL INFILE to import a very large CSV file into my DB. Now with my new server setup this is not allowed. What is the perferend alternative to using LOAD DATA LOCAL INFILE?
<2> cappiz: I'm going off line in a sec, and I'm not the most informed person here anyway :-) seriously though, look at some tutorial on database design. A single integer primary key column isn't a lot of storage, and the database handles it very well (much better than an arbitrary text/blob field)
<5> jedwards_, what do you mean by "not allowed"?
<7> beebum: with the new version of mysql i have installed its not setup to allow this. http://dev.mysql.com/doc/refman/4.1/en/load-data-local.html
<3> hehe
<7> beebum: seeing that its a potential security risk is there a better way to get this large fine into the DB. I tried LOAD DATA INFILE w/o the local and the process errors saying it can't get stat of file.
<3> roger osfameron
<7> large file*
<5> have you tried the --local-infile=1 option with the client?
<7> no, I currently am only accessing it via php. Is this possible with this? I'm not the admin over this particualar server and getting a hold of this guy to make changes takes a while.
<8> Why is that even an option that can be disabled? Any file you can read locally you can parse and feed to mysql with INSERT...
<5> i don't know how to specify that option with php
<7> not sure jst something mysql decided to add. that page i linked talked soem about it but seems everyone is pissed about it
<5> yeah, people don't like being secure
<7> lol im all for secure. But make it work with me! =)
<8> beebum, how does it make anything secure?
<5> with the option enabled by defaule makes it less secure
<8> how?
<8> anything you can read locally you can insert. why forbid batch inserts with LOAD DATA?
<5> i don't know, that just what i read in the docs
<7> here's whats in docs
<7> There are two potential security issues with supporting the LOCAL version of LOAD DATA statements:
<7>
<7> The transfer of the file from the client host to the server host is initiated by the MySQL server. In theory, a patched server could be built that would tell the client program to transfer a file of the server's choosing rather than the file named by the client in the LOAD DATA statement. Such a server could access any file on the client host to which the client user has read access.
<7>
<7> In a Web environment where the clients are connecting from a Web server, a user could use LOAD DATA LOCAL to read any files that the Web server process has read access to (***uming that a user could run any command against the SQL server). In this environment, the client with respect to the MySQL server actually is the Web server, not the remote program being run by the user who connects to the Web server.
<7>
<9> dude
<9> there are two potential problems with flooding a channel, one you'll piss people off, two you'll piss people off
<7> lol sorry
<7> no other convo's were going on figured it wouldnt interrupt them
<5> kinda filles the logs tho :(
<7> ahh gotcha
<5> s/filles/fills/
<8> I don't consider a hacked mysql server to be an important threat model. It could be fixed by having the client library cache any LOAD DATA LOCAL INFILE queries and only permit the server to request those particular files.
<5> vandemar, i think it's for the sake of people that load things like xamp, not people that have a working knowledge of security
<5> of course many security initiatives are just theoretical anyway
<8> what's the point of disabling it on the _server_, anyway? If the server's hacked, you think they're not going to enable that option while they're hacking it?
<8> it's a client vulnerability; the client library should have an option to disable local file reads, and that's that.
<5> it was my understanding that disabling it was to "hopefully" help prevent hacks in the first place, i could be wrong
<10> hi Can I get a dump of all recods in a table?
<8> mysqldump
<10> thanks,
<5> vandemar, it was my understanding that it works like this, disabled by default from the server side but can be enabled manualy from the client when needed. again, i could be wrong
<11> hello
<11> how can I make a count(*) return 0 ?
<12> delete from table; might do it
<5> don't have any records?
<11> I have this: SELECT count(*) FROM table WHERE word LIKE "KABUMM" GROUP BY word
<11> i want to get a zero from it
<11> but I dont get it...
<12> delete from table where word like "KABUMM"
<11> i did something like IFNULL(count(*),0) but that doesnt work either
<11> i dont want to delete
<12> so what are you really asking?
<9> why group by word?
<11> it could be word, by id, by whatever
<9> just select count(word) from table where word like 'kabumm'
<11> what I want is to be able to get a 0
<5> Target0, you want the query to lie?
<9> what cj suggested works fine for that
<9> count(*) should never return null
<11> lie? if there isnt any records, a 0 aint a lie....
<5> so what does SELECT count(*) FROM table WHERE word LIKE "KABUMM" give you?
<11> nothing
<11> it doesnt give me a 0
<11> gives me nothing
<11> no rows
<5> ah, i think i see what you are after now
<5> try SELECT count(*) as count FROM table WHERE word LIKE "KABUMM"
<11> and I want a row, with a number... if I cant find nothing I want a 0 on it
<11> still nothing
<9> pastebin the query and result
<5> strange, i get count(id) with value of 0 on my test
<11> SELECT count(*) as count FROM dic_pt WHERE palavra LIKE "XAlicerce" GROUP BY palavra_id
<11> the result is on mysql browser
<11> so... no past...
<11> I know how to do this, when I try to relate with another table
<13> when I try to create a procedure I get the following error, Table 'mysql.proc' doesn't exist
<11> realting with another table with join left and stuff, returns nulls or gives 0 on the counts()
<5> Target0, remove the group by part
<11> that works
<11> but this had a point. if it did find something I wanted to return the word_ID
<9> so return the word_id
<11> I cant, cuz I have to group then
<9> uhm, why?
<11> if I have select cout(something), something from.... I need a group by
<11> or cout wont work
<3> hum... it seems like the FK i make doesnt get stored or soemthing...
<3> once i make them... they dont show up in the list
<3> using mysql administrator
<14> InnoDB tables?
<3> ?
<14> Are you using InnoDB tables?
<3> no
<3> MyISAM
<14> Maybe you should.
<15> lo
<11> oh well, never mind, all this work and I can solve this with a result number or something
<3> will: why?
<14> Because MyISAM does not support FKs.
<14> Because InnoDB does.
<14> Target0, What did you need?
<3> oh ? thought they did.. :S
<14> I believe it will soon.
<14> Just not now.
<8> they're on the roadmap for 5.2
<3> will: the DB i got has FULLTEXT KEY `ft_name` (`ft_name`)
<14> That ****s.
<3> that isnt supported under InnoDB
<14> Then you don't get FKs or FTI.
<14> Nope.
Return to
#mysql
or
Go to some related
logs:
fgrlx FC5
#lisp
ucarpctl
#physics
GTK_CONFIG experiment
perl selfmodification
inkscape internal compiler error Segmentation fault
grub loading error 22 ubuntu
force clvm removal ubuntu
#lisp
|
|