Hi Serge,
A version supporting MySQL 4.1 would be great!
The link to the modified version of CocoaMySQL is=20
http://www.theonline.org/cocoamysql/
The person who did this version wrote me the following about how to=20
build the modified framework:
"I started off grabbing the latest 4.1 install package off of the mysql=20=
site and installed that. =46rom there I got the latest SMySQL framework=20=
source. In that project opened in xcode I removed all the included=20
mysql libs and headers and instead pointed/linked them over to the 4.1=20=
version installed now in /usr/local/mysql. One thing I did have to do=20
to make it actually compile was define the MYSQL_CHARSET. The 4.1 mysql=20=
headers did not have a default charset defined, so I just tossed it in=20=
as "latin1" into one of the SMySQL header files. =46rom there I just=20
built the framework in xcode then copied it over/into the CocoaMySQL=20
project. It seemed to work, so I went with it."
I received the following problems with the modified framework:
- "my varchar and text fields are all in unicode (ucs2 or utf8). there=20=
was a problem with utf-8 display (some strings are fine but most are=20
truncated or set to null by cocoamysql.). I hacked around a little bit=20=
and found the problem (NSData to CString to NSString can not handle=20
double-byte unicode when the first bye is x00), patched it, but=20
couldn't get it to compile on my machine (libsqlclient version=20
problem).
before i gave up I found out that if you send a 'set names utf8' query=20=
to mysql then everything just works. so it became my favorite custom=20
query string. maybe you can hardwire this into the program when utf-8=20
client encoding is selected."
- "I tried the user modified version of CocoaMySQL. I could indeed log=20=
into MySQL 4.1 server using it. However, all my data in Korean=20
(encoded as UTF-8) were shown as ????. So I guess there is a bug with=20=
character encoding/decoding in this specific version.
Normally, I use original version of CocoaMySQL with MySQL Server 4.1=20
(with user password hashed with OLD_PASSWORD() function). Under this=20
setting, character encoding/decoding works perfectly both with UTF-8=20
and EUC-KR. However, I had difficulties with UTF-16 encoding. Is this=20=
a known issue?"
Best Regards,
Lorenz
On 24. Feb 2005, at 07:56,=20
mys...@li... wrote:
> Hi Scott;=3D0D
> =3D0D
> I'm away, not being able to spend much time on SMySQL... have to=20
> answer =3D0D=3D
>
> a couple of late questions as well.=3D0D
> To keep it short, I'm working on a big improvement of SMySQL, among =
=3D0D
> other thing it will use the new library libmysqlclient so it will be=20=
> =3D0D
> able to connect to 4.1/5.0.=3D0D
> It will also include a 'MCPEntrepriseKit' doing relation/object =3D0D
> modelling.=3D0D
> =3D0D
> Serge.=3D0D
> =3D0D
> PS: I kind of remembered some one sending me a pointer to a version of=20=
> =3D0D=3D
>
> CocoaMySQL which contains a binary of the framework using the new =3D0D
> library, hence working OK with server version 4.1/5.0... but can not=20=
> =3D0D
> find the link anymore.=3D0D
> PPS: I'll try to answer all question for which I'm late, as soon as I=20=
> =3D0D=3D
>
> get a bit of time.=3D0D
--=20
lorenz textor
** sh **
eigerstrasse 21
8200 schaffhausen
tf 052 - 624 27 91
** zh **
schimmelstrasse 5
8003 z=FCrich
tf 043 - 333 00 19
**
mobile 076 - 531 71 74
email lo...@te...
|
