| |
| |
| |
|
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
Comments:
<0> no dice
<1> Then you did the file wrong somehow ;)
<1> Or
<0> [mysqldump]
<0> p***word=xoxoxox
<1> you are p***ing -p option :D
<0> cut and paste
<1> which will force it to prompt
<0> OH
<0> yeah
<1> hehe
<0> perfect :-)
<2> Therion: lol, I think I found the problem, and it is going to be super stupid!
<2> the netmask of the server!!
<2> well of one of the clinets
<1> heh!
<2> should be /28,
<2> but srv2 is a /27
<2> well the other way around
<2> I think it confuzes mysql
<3> does anyone know what people used as an alternative to group_concat on mysql versions < 4.1 where they first added that function
<2> Therion: nope, netmask was not it :(
<1> section3: non-SQL code.
<3> Therion, ouch
<3> that ****s
<3> hah
<4> if I am expecting to get data and know it is only going to resulkt in one row, is there any optimization advantage to doing LIMIT 1?
<1> !m Kaitlyn optimizes limit
<5> Kaitlyn: (How MySQL Optimizes LIMIT) : http://dev.mysql.com/doc/mysql/en/LIMIT_optimization.html
<1> Kaitlyn: read that and decide
<6> Therion: how can i used the default setting for the mysql replication? if i dont have the cnf file? any doc or manual on it?
<1> !man replication
<5> (Replication in MySQL) : http://dev.mysql.com/doc/mysql/en/Replication.html
<6> ok....
<7> Hi - I need the "client library that comes with MySQL 3.x" for TeamSpeak to use a 4.1 server. What file do I need?
<7> I downloaded mysql-3.23.58-pc-linux-i686.tar.gz, but don't know what to look for.
<7> libmysqlclient.a in the lib/ dir?
<7> Er, I need the devel - where can I get 3.x devel?
<8> what happens if i delete the contents of /var/lib/mysql?
<7> The contents of /var/lib/mysql will be deleted.
<9> most likely your server will stop working
<9> 'night sim
<10> Hi, can some one please tell me why I am seeing errors like this when I import a dumpfile: ERROR 1062 at line 32619: Duplicate entry '13763' for key 1
<11> because you have a duplicate key
<10> Since this Database has grown very large I see this more often
<10> then I have to run repair, export, then it works fine
<10> firewire, thats obvious but my question is why am i seeing it more often these days with that database ?
<11> so if you run a repair table and then do the same insert again it works?
<10> yes
<10> i am actually dumping the database then importing it on a different host evey day
<10> and every so often I get the duplicate key issue
<10> and it is becomming more frequent as the database grows, that what i experience
<11> ok so you aren't actually running a repair tab
<10> well
<11> you're dumping the data and importing it
<11> that's WAY different
<10> the dump and the import to a different host gets triggered by cron at modningt. So in the morning my cron daemon mails me that there was a problem ie duplicate keys, then i run the repair and do the dump -> import again
<10> then it works
<10> any reason why these duplicate keys keep on appearing more frequently now a days ?
<11> why are you dumping and importing this data each night?
<10> i have a production box
<10> and a live box
<10> midnight production gets exported to the live box
<10> besides that, it also backs up the production box every midnight with the dump
<11> which box has the duplicate keys?
<10> the production box
<10> the dumpfile that comes from the production box has a duplicate key some times
<11> so when you import on to the live box you get a duplicate key error?
<10> yes!
<10> :)
<11> which table?
<10> does it matter
<11> oy
<10> what do you mean which table
<12> use a WHERE clause to filter out the duplicate keys, or use INSERT IGNORE ...
<10> you want the name of the table
<11> no
<12> or better yet, figure out WHY you're getting duplicate keys.
<11> I want to know if the table you're importing into gets inserted into from the live site
<11> infi that's what I'm trying to find out
<10> ok, i dump the table, then import
<10> table for table
<10> so every import dumps the table, then recreates it on the live box
<11> is anything else accessing those tables?
<10> the webserver scripts
<11> are they inserting into the table?
<10> yes
<11> how are you dumping and importing?
<10> here: /usr/local/bin/mysqldump -h10.0.0.50 -ugoofy -pgoofy2 --databases --add-drop-table dcdns > /usr/home/douw/backup/bigboy/db/dcdns-$today.sql
<10> thats the dump
<11> does that include lock tables?
<11> if not then no **** you're getting duplicate keys
<10> "/usr/local/bin/mysql -hlocalhost -uroot goofydb < /usr/home/douw/backup/bigboy/db/devnet2-$today.sql
<10> thats the import
<11> yeah that's probably why
<10> aha
<10> so I have to lock the table when i import the dumpfile ?
<11> so if your import tries to ***ign the explicit ids 1, 2, 3 and after 3 your website does an insert then the dump is going to collide on key 4
<11> err id 4
<10> ok
<11> or you could not do all that dumping/loading
<12> phpxyz: is your primary key an auto_increment field?
<10> yes, autoincrement
<10> but
<11> no buts
<10> the import on thwe live server, that live server never inserts
<11> damn it!
<11> you said it did!
<10> the live server never inserts records, ony reads
<10> ****, sorry
<12> phpxyz: in your dump script, you could write a wrapper to take the maximum key size, truncate the table and reset the AUTO_INCREMENT to max_key_size+1, then do your import. then, all of the web scripts could go on inserting as normal.
<10> it inserts when it is importing
<12> oh, nevermind.
<11> try using --opt with mysqldump
<10> maybe lock tables will help
<11> maybe
<10> it's just funny that this starts happening as soon as the database starts getting big in size
<10> before it never use to be a problem
<10> i will try lock tables when importing
<11> well you're doing something stupid somewher
<11> I'm tired of digging for it
<10> well, then the stupidity only started showing the other day, and for a year i never got any issues
<10> thanks for the advice though
<10> ciao
<13> hello
<13> why error #1264 on
<13> latest stable version
<14> hi all
<14> does mysql have multi-processor support?
<15> yes
<13> hello
<14> is it native support, which can be turned on/off at compile time, and later used to utilize both (on 2-cpu box) processors?
<11> uhh
<11> mysql is threaded
<11> it's "multi processor" by default
<15> DuskoDugousko: i dont think you can turn it off just like that.
<13> why error 1264 and it saz #1264 - Out of range value adjusted for column 'id' at row 1
<13>
<15> download the source and check the ./configure options
<11> the only way to "turn it off" is to use the embedded server
<13> any idea?
<13> version latest stable 5.1.8
<11> is id an auto increment
<13> yes
<11> did you try to give it a negative value or a value too large?
<11> I've never seen that error
<13> it's from phpmyadmin
<13> usually it auto increment when insert form
<13> fine on old 3 version and 4
<11> oh boy
Return to
#mysql
or
Go to some related
logs:
ubuntu add megaraid2
Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an eb
about the jesesus
437A Serial ATA Controller debian
NOPPENLINUX
ubuntu cannot access windows shares over smb
fedora pt_chown
#python
#perl
keybind winamp
|
|