Re: Databasing and Cocoa
Re: Databasing and Cocoa
- Subject: Re: Databasing and Cocoa
- From: Serge Cohen <email@hidden>
- Date: Mon, 1 Mar 2004 00:29:48 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi again James;
for more information on my implementation of MySQL support you can go
to the web page of the framework:
http://mysql-cocoa.sf.net (general page)
http://mysql-cocoa.sourceforge.net/SMySQL_doc/ (API documentation)
It is being used by at least a couple of project (one being the
cocoamysql project I was pointing in my previous eMail), so in a way
I'd say it is there already (indeed it's already version 2.2.1 -updated
today to 2.2.2, solving the issue I mentioned in my earlier mail-, and
I don't get complaints about stability).
The 'trouble' of the GPL, is that if you release the software, you have
to release the source (of the whole software, not only of the
framework)...
Since release 4. of mysql, the GPL licence makes it clear that any
software which is using MySQL as sole DB engine should either get a
licence (from MySQL AB) or be released under GPL (meaning, release your
sources). So even if your using my framework as is (as a dynamic linked
object), you have to release the source of the application.
Still, if you are solely using the software for 'internal' use (no
public release/distribution), you don't have to release sources or
anything alike.
The idea to separate the Object layer from the DB layer is a very good
(and 'common') one. You will be (very likely) interested by the
EOF(Entreprise Object Framework) part of WebObjects, which is well
documented by apple
(
http://developer.apple.com/documentation/WebObjects/
WebObjects_Overview/EnterpriseObjects/chapter_3_section_1.html#//
apple_ref/doc/uid/TP30001008-DontLinkChapterID_4) ... this might
provide you with some good design practice for separating the 2 layers.
I'm thinking to make this kind of separation easier to implement using
my framework, but that will require some time (which I don't have
enough yet)...
Le 29 fivr. 04, ` 22:28, James Tichenor a icrit :
Hi --
Good to hear people are working on the MySQL/Cocoa connection --
surprising it's not there already.
Can you explain a little bit about the GPL, and the changes that have
or are coming about with the next release of mySQL? What is that is
the new license that is making people wary of using the database?
I am starting to think the best method to implementing this software
is to write the cocoa app independent of reliance on any one database,
at the moment, encapsulating all my data away from the database calls.
Then depending on the system that we decide is best/most
affordable/most stable/most supported for the software, we can write a
plug to the db then.
But having said that, I'd love to learn more about your framework and
see how it works. Do you have any ideas why you are not getting a lot
of freedback/new requirement requests?
James
- ----------------------------------------------------
Serge Cohen
GPG Key ID: 9CBB58FB
- ----------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAQnXx5EPeG5y7WPsRAjapAJwPR+bs+ytKcanLZU+u8Ly3QsaZ1gCfZ50C
Qsa/GYK1DYqn+xFcukgN5Y8=
=MMVz
-----END PGP SIGNATURE-----
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.