| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Comments:
<0> mmmmmm
<1> I'll be damned... that worked!!!
<1> wtf?!
<0> good
<2> any guide with instructions on running 2 copies of mysqld on the same machine?
<1> good is right... I just don't get how or what or why... ?!
<0> looks like problems with bdb in your version of mysql
<0> who knows why
<1> hehehe... what should I do now?
<0> is the server working?
<1> gleam_: it is... and the forum software is back up and running...
<0> you might need to run mysql_fix_privilege_tables
<1> i was just going to ask whether I should continue with those instructions...
<0> yeah
<0> keep going
<1> gleam_: thank you so much... you saved me a nights sleep... I've been killing myself here for the past 2hrs...
<1> thank you thank you thank you!!
<0> sure
<1> hehehe.. i'll definitey keep going... hopefully i can finish these instructions without further problems
<1> awesome... just finished... thanks again, I really appreciate it!
<3> greetings mysql gang! I've run into a problem that I _suspect_ may relate to collation problems and I thought I'd toss it out here to see if anyone might be able to give me some leads.
<3> I've got very marginal mysql knowledge so my apologies in advance if i ask the obvious.
<3> I'm working with Dada Mail and using mysql for storing the archives.
<3> The problem comes up when some emails contain certain html entities - nothing too fancy - curly commas or quotations.
<3> They are getting translated into the html entity code - such as ’
<3> this is presenting 2 problems back to Dada Mail:
<3> 1) these characters are not being displayed properly
<4> Lynnwood: Ask the author of Dada to support these entities.
<3> 2) They are actually causing some scripts to fail with reference to a "wide character"
<3> Xgc - yes, i have. not much help, i'm afraid. He didn't have any answers. I asked if it might have to do with collation settings (which seemed like likely point of problem) but he said he knew nothing about that.
<3> so I guess my questions are along these lines:
<4> Lynnwood: The author of some Mail system knows nothing about the issue?
<3> Am i right at looking at possible collation problem - or problem between encoding in Dada and collation.
<3> yea. what can I say...
<3> mysql is only one of the store optoins for the program.
<3> but he did recommend it for some of the options I'm using.
<4> Lynnwood: Storing to MySQL is a direct option of this program? Where did the DDL come from for the tables?
<3> he provided some basic table definition files - but they did not address collation settings at all.
<4> Lynnwood: Post the DDL (create table statements).
<3> thanks so much! just a sec...
<3> ok, here's the one for the archive, and is typical:
<3> CREATE TABLE dada_archives (
<3> list varchar(32),
<3> archive_id varchar(32),
<3> subject text,
<3> message mediumtext,
<3> format text,
<3> raw_msg mediumtext
<3> );
<3> not much too it.
<3> so I guess i'm just looking for any suggestions of possible directions to explore.
<3> I understand that this may not be - or probably isn't - a problem with mysql, per se.
<3> i'm just hoping to get some ideas where the problem with how dada mail is interacting with mysql might lie.
<3> Or if there's some obvious problem with how i have mysql set up.
<3> i currently have the collation set to utf8_general_ci for all 3 tables.
<3> any suggestions if some other setting might be better are welcome...
<4> Lynnwood: Post is a term we use for data placed in a pastebin.
<4> Post <> Flood channel.
<3> gotcha. my apologies.
<4> Lynnwood: what character set is being used by the mail application?
<3> just a sec. let me double check
<5> hi all. building php thread-safe w/ mysql/pdo ... need to link against ONLY libmysqlclient_r.
<5> even tho my LDFLAGS = "-L$/path/to/lib/mysql -lmysqlclient_r" i end up with BOTH libmysqlclient.15.dylib & libmysqlclient_r.15.dylib. what do i need to fix/change?
<3> charset English (en) iso-8859-1
<3> bb in a sec...
<4> Lynnwood: Hmmm.. Those characters came from that character set? Then you should be able to use latin-1 in MySQL.
<3> granted, i believe they mostly came from macs using MS email clients.
<3> the problem emails, that is.
<3> but they were being p***ed through the Dada mail problem.
<4> Lynnwood: If Dada is using/limited to iso-8859-1, then you should be able to support anything it throws at you with latin1 or probably utf8.
<3> one would think... but somewhere these characters are creating a problem.
<4> Lynnwood: If it's generating something outside that character set, yell at the author.
<4> Lynnwood: Your main problem may be that you are not specifying an explicit collation/character set in MySQL.
<4> Lynnwood: You should try that first.
<3> that's what i've been playing with. i.e. manually setting collation setting beyond what was provided in those setup scripts.
<4> The setup has nothing,
<3> admittedly doing it kind of blind, not really knowing what collation is all about.
<3> but I've tried several of them - and then ran checks on the tables to make sure they were ok.
<4> Lynnwood: http://dev.mysql.com/doc/refman/5.0/en/charset-table.html
<3> and then trying to send through an email that would create problem - and still see these problems arize.
<4> Lynnwood: Which character sets did you really try?
<3> latin1_bin, latin1_general_ci, latin1_general_cs
<3> for some unknown reason, it was initially set at utf8_latvian, which is what had me start looking at the collation setting because i was pretty confident _that_ wasn't right.
<3> i've thought about trying ascii_bin but don't think i have try that yet.
<3> bbib - phone call...
<4> Call from Latvia?
<3> :-)
<4> Lynnwood: You might just stick with latin1 for now. CREATE TABLE blah ( ... ) DEFAULT CHARACTER SET latin1; -- or utf8
<3> can i change an existing table?
<4> Lynnwood: ALTER might be able to do that. But you can always CREATE a new table and copy the data.
<3> ok
<3> i'm working in phpMyAdmin
<3> and the most basic latin1 listed is latin1_bin
<4> Lynnwood: Just look at the ALTER syntax. You'll see how to do it.
<3> ok. i'll give it a try. thanks for the lead!
<3> i'll commend you to my latvian cohorts
<4> Lynnwood: Try latin1 or utf8 for the character set.
<4> Lynnwood: mysql_prompt> show character set;
<4> Lynnwood: For latvian's, maybe latin2.
<4> or latin7. :)
<3> i tried mysql_prompt> show character set;
<3> and now i'm newly confused. for latin1, is shows the default collation as latin1_swedish.ci
<3> which i remember now was the original collation setting.
<3> not latvian - but just as odd to me.
<3> how about trying plain ol' ascii US ASCII ascii_general_ci
<6> Hello folks
<6> check this out ..
<6> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
<6> 12661 mysql 20 0 387M 348M kserel 1 18.7H 150.54% 150.54% mysqld
<6> How can I make mysql show me the complete query in the show processlist output;
<7> where can I find a list of all the valid commands.. like select join between and or etc etc...?
<6> I have a => load averages: 1.11, 1.20, 1.19
<6> Is top lying or are my eyes twitching :D
<8> anybody know how to create stored procedures with phpmyadmin, which are longer than one line long?
<8> it seems the "delimiter" command don't work.
<8> errr = http://dev.mysql.com/doc/refman/5.0/en/data-manipulation.html
<7> thanks
<9> if you just enter it into phpmyadmin it doesn't work?
<9> do you ahve to use a delimiter when you execute a stmt through phpmyadmin?
<8> well, if you want to write multi-line stored procedures, apparently you need to change the delimiter
<8> so that you can store the ";" in the procedure
<9> what do you see if you try to send "CREATE PROCEDURE TEST() BEGIN SELECT 1; END" ?
<8> "#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT 1' at line 1 "
<9> lame
<8> indeed.
<9> no phpmyadmin documentation that explains it?
<8> i'm looking...
<8> looks like you can't use phpMyAdmin to create stored procedures.
<8> damn
<9> heh
<9> not even in a .sql file?
<8> hmm... thats a thought
<8> i'll give it a shot
<0> yawn
<0> how are ou setting the delimiter?
<9> it's lame that you can't do thsi though, it should be easy enough
<8> "delimiter $"
<0> darn
<8> doesn't look like it works in an imported .sql file either
<8> stupid.
<0> i dunno, that works for me
<0> weird
<9> gleam_: works for you in phpmyadmin?
<0> no
<0> on the cli
<9> zaydana: do you need to upgrade phpmyadmin or somethign?
<8> got 2.8, so I don't think so
<9> gleam_: well of course it works there, but that's not what's being discussed here :)
<0> oh
<0> well nevemrind me
Return to
#mysql
or
Go to some related
logs:
lvm No program
#awk
dagmar striping
ubuntu radeon x800 apt-get
oninoshiko
gst-register ubuntu
php4 debugprint
i-lines sucks
#linux
#perl
|
|