Re: Databasing and Cocoa
Re: Databasing and Cocoa
- Subject: Re: Databasing and Cocoa
- From: Serge Cohen <email@hidden>
- Date: Sun, 29 Feb 2004 18:00:01 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there;
I just wanted to mention the SMySQL framework (mysql-cocoa.sf.net) that
I'm developping under GPL (which makes it available to any in-house
software)... This is a framework for using MySQL within a Cocoa app (in
Obj-C).
The main problem I see about right now is that the released binary has
one small problem (one file missing), but the CVS tree is Ok, and I got
a couple of positive feed-back (about stability and possibilities), one
of which (cocoamysql :
http://cocoamysql.sourceforge.net/) is a general
front end to MySQL written in Obj-C (also under GPL, so you can use the
sources as example for your own app).
It is true that SMySQL framework have not evolved for the last months,
but this is only partly due to my lack of time to devote to it, the
other reason is the lack of feedback/bug report/new requirements from
the community.
If you want to give it a try, I'd be happy to help if you face any
troubles with the integration of the framework in your app.
Serge.
Le 29 fivr. 04, ` 17:31, James Tichenor a icrit :
First response: Check out FrontBase <http://www.frontbase.com/>,
which while not free is inexpensive and has a simple Objective-C API
you can use from Cocoa applications.
I did look at and work with FrontBase quite a bit -- I liked it's easy
of use in setup and was impressed with how simple it seemed to be. I
was a little confused as to it's Obj-C support, thinking it had
stronger Java support with Obj-C as an afterthought, but I wasn't
sure. The biggest stumble was price -- our application is an in-house
system that really needs to be as inexpensive as possible -- basically
all costs come out of my own pocket. Plus, I really like the open
source solutions and want to support that community. Kind of surprised
that the mysql system is not more robustly supported by Cocoa --
someone has to write a solid framework! I'd do it if I knew anything
about it :-)
But maybe it would be smarter, considering I am teaching myself Cocoa,
to make the database part of it as simple as possible for now and port
to mysql when support becomes more consistent and solid.
Often object-oriented applications that interact with relational
databases use a mapping of class<->table, instance<->row,
attribute<->column, relationship<->foreign key column with join.
Thank you, that's what I suspected. Whatever makes the most sense
seems to be the smartest way to implement, most of the time.
I strongly suggest at least going through the WebObjects tutorial.
You can see the philosophy it uses and then emulate that, even if you
don't actually wind up using WebObjects for your implementation.
Yes, I will look at WebObjects next.
James
_______________________________________________
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.
- ----------------------------------------------------
Serge Cohen
GPG Key ID: 9CBB58FB
- ----------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAQhqY5EPeG5y7WPsRAqVKAKDS+zb5nQcLmkgL2NwngAktS6AS8QCePmeR
tNIz7bMHR5k4XYpqmXBY7j4=
=oN6G
-----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.