Re: [Mysql-cocoa-users] SMySQL framework with MySQL 4.1

[Lorenz T. <lo...@te...>]

Hi Serge,

Thank you very much for taking the time to answer!

> Hi Lorentz;
>
> I was wondering if this is not a good time to go for the 2.0 API of=20
> the framework.
> This will mainly mean that you have a to a 'Massive' Query/Replace=20
> (for changing the SMySQL prefix by MCP).
> The name of the methods are unchanged, so only the class names have to=20=

> be changed.
I plan to switch to the new version for the next release of CocoaMySQL.=20=

If only the class names changed, it's really not a great deal to make=20
the necessary changes.

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

> me to keep distributing the old version of the framework), I'm ready=20=

> to help you as much as possible if there is anything I can do for=20
> making it easier for you to go from version 1.0 to 2.0 of the=20
> framework.
Thanks for that! I'll send you a mail if I have problems using the new=20=

framework.

>
> The nice thing about the new version is that it uses the=20
> libmysqlclient (instead of having its sources in the project), so it=20=

> is much easier to get it to work with a specific version of the=20
> library. The one distributed is 4.0, but in the context of the=20
> previous paragraph, I can make a target using 4.1 version of the=20
> libmyslqclient.
A version using MySQL 4.1 would be great. I think this would work well=20=

with MySQL <4.1, but would add the possibility to connect to servers=20
running 4.1. I hope that it's not too much work to make this changes.=20
Please tell me if I can help!

>
>
> 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)?
Definitely NO! Developers who are using an old version should make the=20=

changes themself!

> 2. What can I do, to make the 'jump' easier for you?
I think it's perfect as it is now. It's just because of my laziness=20
that I haven't made the jump yet ;-)

Thanks for your work on the framework,
Lorenz

>
> 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/XI9Y5EPeG5y7WPsRAofMAKDsyv6Yz59Ezvh0sldIyybyZ2PrugCgt0Fq
> vNHQN9HAkTu1su1X1L38BgM=3D
> =3D4cBD
> -----END PGP SIGNATURE-----
>
>
>
>
>

--=20
lorenz textor
** sh **
eigerstrasse 21
8200 schaffhausen
tf 052 - 624 27 91
** ticino **
via delle scuole 41
6963 pregassona
tf 091 - 940 20 57
**
mobile 076 - 531 71 74
email lo...@te...