Re: MySQL and Cocoa
Re: MySQL and Cocoa
- Subject: Re: MySQL and Cocoa
- From: Markus Guske <email@hidden>
- Date: Sun, 24 Feb 2002 14:00:18 +0100
Hi,
>
Date: Sat, 23 Feb 2002 18:18:51 -0600
>
To: email@hidden
>
From: Chris Hanson <email@hidden>
>
Subject: Re: MySQL and Cocoa
>
[...]
>
Eduardo:
>
>
There currently isn't any database access in the Cocoa frameworks.
That is really bad. This was the answer, I got a weeky ago too.
>
There actually isn't any standard database access layer in Mac OS X
>
at all. There used to be a technology called the Enterprise Objects
>
Framework that was the best data access layer on the planet. Now
>
unfortunately it's only available from Java and only as part of
>
WebObjects; Apple discontinued the Objective-C version and actually
>
never shipped it for use with Cocoa and Mac OS X.
This is what - I assume everybody - didn't understand.
I still have a NEXTSTEP 3.3 Developer Edition for Intel here and
surprisingly there is an extra CD included with EOF 1.1 inside.
This was a good solution. Offering frameworks as a standalone
bundle. --> Btw. this is what object-orientation promises: Reuse your
frameworks in different projects, and don't develop it only for special
purposes.
I could image, that there are many of us out there who want to develop
great software which needs a quite good and working database layer.
And if we have to develop software which needs a DB-layer, we don't want
to reinvent the wheel each time we need DB access.
I also understand the Apple decision to "buy a ticket for the Java
train", currently this is mainstream.
But I couldn't understand why they didn't sell the EOF as is as a Obj-C
framework.
Maybe, they don't want to get in trouble if anybody finds an error in
this framework.
I am very disappointed, that they close this "file".
>
>
For database access now you'll have to use your database's C access
>
library if one is available. I'm pretty sure there is one for MySQL.
Yes, e.g. take a look at the O'Reilly MySQL/MSQL book. You find examples
in C and C++ how to access databases from the C-API.
The C++ Examples shows a way how to build up a little framework for this
purpose.
>
Or you might be able to write some Java code that uses JDBC, and then
>
call that code from your Cocoa application via the Java bridge. (If
>
you've written your Cocoa application in Java, you don't even have to
>
do that.)
This is the other way, but are there any measures on performance using
this way?
This could be quite interesting. Does anybody know if somebody tried it?
>
>
I can't recommend strongly enough that anyone and everyone who even
>
remotely might need database functionality -- whether for an
>
enterprise application or a consumer desktop application -- file a
>
bug with Apple at <http://bugreport.apple.com/> requesting they add a
>
standard database access layer to Cocoa. It's critical to a great
>
number of us, and the only way Apple will get the message is if it
>
comes in through the feedback channels they pay attention to.
Yes, this could be a good way to do. But I don't think that Apple ever
will. But I will report this "bug" also.
One more point: One of the biggest advantages of the Java
language/frameworks is, that SUN listens to their customers and offers
"everything" as a standard library.
E.g. 2D/3D graphics, Serialization, Mail-API, JDBC and so on. Many of
them were asked by their customers/users and SUN decided: "Yes, the guys
out there seems to need it to get a full set of standard libraries, we
give it to them as a framework".
This is great and one of the main reasons why Java is so successful".
This is what Apple might learn from SUN. Listen to the market and offer
a lot of useful frameworks, which are e.g. currently developed.
A framework to get access to a database is a must in a commercial market
and the already have one. So again, it is not clear for most of us why
they won't release it again as a standalone framework.
These are my "five cents",
>
>
-- Chris
>
-- who wishes Apple would juts GET IT already and bring
>
back Objective-C EOF as part of Cocoa
>
-- who can't understand how anyone at Apple could ever
>
justify discontinuing Cocoa EOF to begin with
>
-- What were they THINKING?
:-) Only Apple can tell us.
Regards,
- Markus
Markus Guske
http://www.guske.de
Erftstra_e 17
mailto:email@hidden
41564 Kaarst Tel.: +49-2131-769107
Fax: +49-2131-769195
Mobile: +49-173-9461880
_______________________________________________
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.