| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Comments:
<0> anyone have that problem too?
<1> Pieface: in general, yes
<0> Pieface, yes if it's a daemon
<2> im under sql tab for the table i want to alter
<0> that listens on 0.0.0.0
<1> lorfds: did I say the sql tab?
<2> yes
<1> that's funny, I don't see that
<1> I said click on properties for the table
<1> then
<2> there is no properties button
<2> i said that up above
<3> how is a S2 level bug still in analyzing after 40 days with no comments coming from mysql?
<4> people are busy?
<1> lorfds: ok, go back to the main page for the database you're using
<0> xlx, are you paying them?
<2> dp: ok
<3> flip that, are they paying me.. are the companies that get the benefit of my hours of work figuring it out.. paying me?
<1> lorfds: from there, you should see the tables listed, correct?
<2> yes
<1> ok
<0> xlx, they are paying you by allowing you to use it for free
<5> dp_ / t35t0r ... apache was added to rc.local o something like that. (started at the end of boot) which user would that be running under?
<1> in the action column, there should be a series of buttons
<2> yes
<1> Pieface: www-data, typically
<3> t35t0r, um ok.
<1> lorfds: 4th one from the left, looks like a hand?
<2> a hand grabbing a piece of paper?
<1> ya
<2> ok
<1> click that
<1> that's 'Properties'
<1> now, under the column list, do you see "Indexes"?
<2> yes
<1> below that is a text box
<6> In order to avoid a syntax error while uploading a *sql exported from the same version of MYSQL on the local machine to the remote machine, i used chose the option for MYSQL323 Compatibility. This has completely changed the structure of my db. these are the differences: http://selectparks.net/~julian/tmp/stories_local.png http://selectparks.net/~julian/tmp/stories_remote.png. now i can't post new articles or add anything.
<2> create an index on columns?
<1> stating: "Create an index on <box> columns"
<2> yes
<1> change the number there
<1> and hit Go
<7> screenshots of text, oy
<6> is there any way to get around this problem? why does one use the swedish language and the other none at all for collation?
<8> the bug can't be worked on until it's verified, and it's sitting in analyzed state for 40 days.
<1> delire: collation was added in 4.1, IIRC
<7> delire: Because MySQL AB is based in Sweden.
<2> dp_: ok, im there
<0> xlx, if you don't like it then you can use one of the 10 other free rdbms
<7> But why use 3.23 compatibility when you don't want it?
<1> lorfds: now, add the columns that you want to the index
<2> index type = index, unique, fulltest
<9> xllx: Which bug#?
<1> index, normally
<2> also it asks for index name -- im ***uming this isnt important
<1> it's not
<8> t35t0r, what's your problem jack? The high and mighty attitude coming from you, especially with your nick... is a little off base. I doubt for one second you work for Mysql... My comments are directed at people who can do something about it, the high up cl***es.. like Therion and the rest of them.
<8> Not as some troll that tries to align himself in irc battles.
<6> mendel: right..
<6> mendel: because of this syntax error during upload.
<0> ?
<2> ok -- so now the primary key will be a combination of the two fields, dp?
<10> t35t0r; me to got the same error
<1> yes
<0> amoi, the problem was the device ran out space heh
<0> amoi, i checked the /var/log/mysqld.log should have done that first oops
<2> bam
<2> thanks dp_!
<1> np
<6> mendel: are the differences i'm seeing there due to the 323 compatibility?
<7> delire: If that's the only thing you changed, then yes.
<6> mendel: why is it that when moving from identical versions of mysql am i getting syntax errors? local and remote machines are practically identical.
<7> What do you mean, "moving from"? You exported it, requested compatibility with an ancient version of MySQL, and then didn't use that ancient version.
<7> It's not identical if you change it.
<7> Why not try to fix the syntax error, instead of using an option that only happens to fix it?
<6> mendel: i export on the localhost without compatibility changes and attempt upload and this error occurs during import.
<6> mendel: i was told here by someone that seemed knowledgeable that going for 323 compatibility would evade this problem.
<6> mendel: apologies, i'm a programmer but know little about mysql.
<7> What do you want me to do? You did something and it didn't work the way you wanted. Now try it the other way and see what happens.
<6> mendel: i'll see if i can generate this error again. perhaps current company may be able to shed light.
<6> mendel: FYI my primary question is why there would be syntax errors between indentical versions of mysql. can export and re-import the same *sql locally, yet from here to the remote machine, this error occurs...
<7> delire: That depends completely upon the error.
<7> The solution to the general case would be very hard to find and of no use to you in fixing your specific problem
<8> delire, i'm thinking you need the shared-compat library ...
<7> Wha?
<8> there's an rpm that allows backwards compatibility.. i don't use it.. i think it's called mysql-shared-compat-323 or something
<11> two sql servers both on soekris embedded linux flash based systems. I'd like to do cross replication between the two servers so they are both master and slave to each other
<7> xllx: Er, to solve what problem?
<8> mendel, just from his general statements, i'm ***uming that is what he needs
<12> Hi folks, first visit here .. I created tables with the InnoDB engine and set up a foreign key .. however I can't confirm that this relationship exists even by doing Show Full Status From table_name .. is there another way of showing this information?
<11> is that a stupid idea...
<6> xllx: hmm, interesting..
<7> I don't understand what that would have to do with anything at all
<7> There was some syntax error which is a mystery
<8> Shared compatibility libraries
<8> (3.23, 4.x, 5.x libs in same package)
<7> delire used the backwards-compatibility option of mysqldump to work around it
<8> the 323 suggested that .. that's what he wanted
<7> But did not want the rest of the backwards-compatibility bits.
<7> Unless delire has some other program that will not work unless it has backwards-compatible MySQL *libraries* (and would then fail to start at all otherwise) those won't do anything.
<8> i was just commenting on this :
<8> <6> mendel: i was told here by someone that seemed knowledgeable that going for 323 compatibility would evade this problem.
<8> i dunno what else he was saying, didn't see it
<7> xllx: Yes, in mysqldump.
<6> ideally i'd like to import it without compatibility at all.
<2> db -- i spoke too soon -- i am still getting errors for violating primary key
<13> mmm how hard is it gonna be to right a procedure that when an insert/update/delete query is run on any table in a db. It performs the same one into another db ?
<8> oh lol.. --compatibility flags
<8> heh, ok nm
<6> mendel: .. xllx given that both versions of mysql are the same and phpnuke has such an utterly ****e and fragile table structure
<7> Solve the known problem. You have a syntax error. What is the error?
<8> --compatible=name Change the dump to be compatible with a given mode. By
<8> default tables are dumped in a format optimized for
<8> MySQL. Legal modes are: ansi, mysql323, mysql40,
<8> postgresql, oracle, mssql, db2, maxdb, no_key_options,
<8> no_table_options, no_field_options. One can use several
<8> modes separated by commas. Note: Requires MySQL server
<8> version 4.1.0 or higher. This option is ignored with
<8> earlier server versions.
<7> Don't do that.
<6> mendel: it's coming..it's a 15mb db. needs to get around half-way through an upload first before failing.
<14> 3.23 compatibility?
<14> Should not be using any host on 3.23.
<7> By my understanding he isn't, it's just an It Happens To Work fix for an unrelated problem.
<14> heh
<7> but it also Happened To Break other things :)
<6> i notice that phpMyAdmin has an "Allow Interrupt of import [...]" option for large files. is 13MB a large file?
<7> No
<6> ok
<14> If you're on a dial up 28.8k maybe...
<7> Maybe it's a large file to use with phpmyadmin, I dunno. But MySQL can happily handle databases in the terabytes.
<14> It has to do with PHP's settings.
<7> ahh
<14> GhettoJava, Away messages are not necessary here...
<6> mendel: right.. well it's plodding along with this uload.
<15> I just finally got around to upgrading to mysql 4.1 from 4.0 and there is all this new language encoding stuff. What should I be choosing when creating a new DB?
<16> gentlemen .. do i need a mod for apache to work with mysql ?
<7> blue: That would depend greatly on how you would like it to work.
<6> Jon_PB: hehe tell me about it..
<7> jon: Hungarian.
<16> well .. the point is to use it to create some forums
<15> I mean does it matter what I choose? should I just do utf8?
<7> blue: Apache is just a web server
<7> jon: If your application expects utf8, sure.
<15> mendel: why hungarian?
<7> jon: It seemed as good an answer as any to someone asking us what language he should use.
<7> :)
<17> I'd even understand it
<18> hi everyone
Return to
#mysql
or
Go to some related
logs:
TROUBLE in check_mail: creating_partsdir FAILED
perl Don't use bareword file handles
ultrasonic wleding
#ubuntu
#css
#php
gentoo +entropy +poolsize
HOWTO_X-forwarding
edubantu
do_stage ()
|
|
