[Mysql-cocoa-users] =?ISO-8859-1?Q?R=E9p_:_[Mysql-cocoa-users]_SMySQL_framework_with?= =?ISO-8859-1?Q?_MySQL_4.1?=

[Serge C. <ser...@us...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For some reasons, I've sent this mail few days ago... and it's still=20
not appearing on the mailing list. So here it is again.

Hi Lorentz;

I was wondering if this is not a good time to go for the 2.0 API of the=20=

framework.
This will mainly mean that you have a to a 'Massive' Query/Replace (for=20=

changing the SMySQL prefix by MCP).
The name of the methods are unchanged, so only the class names have to=20=

be changed.

In this respect (and also, because CocaoMySQL is the main reason for me=20=

to keep distributing the old version of the framework), I'm ready to=20
help you as much as possible if there is anything I can do for making=20
it easier for you to go from version 1.0 to 2.0 of the framework.

The nice thing about the new version is that it uses the libmysqlclient=20=

(instead of having its sources in the project), so it is much easier to=20=

get it to work with a specific version of the library. The one=20
distributed is 4.0, but in the context of the previous paragraph, I can=20=

make a target using 4.1 version of the libmyslqclient.


Tell me what you think of this proposal...

Serge.

PS: Maybe, I'm mislead , and some other developers are using still=20
version 1.0 of the framework (and does not want to update to 2.0), if=20
this is the case, I'd be happy to get some feed back to know :
1. If I should still spent some effort to try keep 'old' API updated=20
(for each bugs found, should I still correct both versions of the=20
framework)?
2. What can I do, to make the 'jump' easier for you?

Le dimanche, 7 sep 2003, =E0 18:01 Europe/Amsterdam, Lorenz Textor a=20
=E9crit :

> Hi,
>
> Since MySQL 4.1 uses a new encryption for the account passwords, it=20
> seems that the framework can connect to the server only when no=20
> password is set for the given user.
> Does anybody know how to build the framework so that the new password=20=

> format is supported? I have tried replacing the password.c file and=20
> other MySQL source files with the new files in the MySQL 4.1=20
> distribution, but that gives only a lot or errors when compiling the=20=

> framework. It seems that there have to be bigger changes...
>
> Thanks a lot for your help,
> Lorenz
>
> --
> CococaMySQL - A Mac OS X MySQL GUI
> http://cocoamysql.sourceforge.net
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Mysql-cocoa-users mailing list
> Mys...@li...
> https://lists.sourceforge.net/lists/listinfo/mysql-cocoa-users
>
>
>
- ----------------------------------------------------
Serge Cohen

GPG Key ID: 9CBB58FB
- ----------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE/YOND5EPeG5y7WPsRAuT3AKCga/QB3VdFEZETFxmMDMn+vL80XgCfdTLE
CgeCE4ZLjVpqz8v7ivMA/No=3D
=3D+CR/
-----END PGP SIGNATURE-----


----------------------------------------------------
Serge Cohen

GPG Key ID: 9CBB58FB
----------------------------------------------------=