On Wed, 21 Apr 2004 14:07:48 -0500, Mark Matthews wrote: >> I have set the default charset to utf8. When I view my variables they all >> show that utf8 as their value. My URL is as follows: > > What does the JDBC connection _itself_ show? Execute the following query > on a java.sql.Statement, and tell us what comes back, as the values you > have posted earlier (from a connection from the 'mysql' command-line > client) are irrelevent in this situation: > > "SHOW VARIABLES LIKE 'character%'"
I did this and got the following results: (I formatted them) character_set_server = utf8 character_set_system = utf8 character_set_database = utf8 character_set_client = utf8 character_set_connection = utf8 character-sets-dir = d:\program files\MySQL\share\charsets/ character_set_results = utf8 Something I have noticed and not sure if it's a problem but I went into the character-sets-dir directory. I found many xml files corresponding to character sets but I didn't find any utf8.xml. Could this be the problem or indicative of the problem? The database seems to handle utf8 just fine even without this file though. >> I did try the latest 3.1. It still behaved in the same manner and what was >> worse, it broke another page of mine. I started getting an error when I >> tried to display that page. It said: >> >> Unknown type '0 in column 9 of 16 in binary-encoded result set. > > Hmmm....That was fixed in the _server_ after 4.1.1 was released, so if > you're not using a compile from source that was pulled from our > archives, then you will have to wait until 4.1.2 comes out. I see. >> I did a google on this and found others having that problem and it was >> driver related. >> >> http://article.gmane.org/gmane.comp.db.mysql.java/3347 > > You missed the rest of the thread, then, it is actually _server_ > related, and was fixed for MySQL-4.1.2 (not yet released, but available > as source code): > > http://article.gmane.org/gmane.comp.db.mysql.java/3350 Gotcha. > Did you ever look and see what encoding your JSPs are set at? If it's > not UTF-8, you will see this behavior, because JSTL will use the > encodings of your JSPs. It is strange (but not dismisable) that it would > work from stock java bean and not a JSTL tag and that this would be > caused by a _driver_ bug. The JSPs are set to UTF-8. When I was using the SQLServer database if I didn't have it set then yes I got question marks displayed but when I examined the string itself it was unicode. There were no literal question marks there but unicode chars. But in this case there are literal question marks in the string so some type of conversion is taking place before I get to display it. >> I can try the nightly snapshots but this is bad because this project will >> need to be production ready and if it needs to use trial stuff like > this... > > MySQL-4.1 is an ALPHA. The JDBC driver is an ALPHA, and you are using > features that are only in the ALPHA. For this reason you are going to > have to put up with using nightly snapshots and/or doing your own builds > if you want the latest bug fixes. You know, I had forgotten this. When I downloaded it I saw somewhere that it said I should use this for all new development and so that's what I was doing but I'd forgotten that it was an alpha. I'm thinking that for right now for this project I should not be doing this. Even if I get the latest and get this working it's unlikely that I'll find a host that is running it. So while the programmer in me wants to get this working for my own edification I think I need to either go back to SQLServer or to MySQL 4.0. The only thing that I'd be concerned about with doing that is at this stage it'll mean a new troubles as I find out I can't do this or that in that version. So you make a good point and I think that I simply made a poor choice in terms of choosing to use 4.1 at this point and time. I still want to use MySQL for my own personal use but for this current project I think I need to wait for releases. Thanks much for you help. I guess before I go any further I need to update the database to see if the problems I'm having right now are fixed or not in the latest versions. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Stormblade (Shaolin Code Warrior) Software Developer (15+ Years Programming exp.) My System: http://www.anandtech.com/mysystemrig.html?rigid=1683 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
