Databasing and Cocoa
Databasing and Cocoa
- Subject: Databasing and Cocoa
- From: J Tichenor <email@hidden>
- Date: Fri, 27 Feb 2004 11:05:22 -0800
My project: to replace our departmental filemaker pro database with a
new mySQL/Cocoa application.
We are the visual effects department that work a number of TV shows,
and we need our database to grow as we take on bigger and more
complicated projects.
My questions:
-- in designing the database/front end, should I assume that any table
I can split data off onto would also be a good candidate for a custom
class in the application -- ie: one table describes the essentials of
what makes a VFX shot special -- it's name, a link to the people who
are working on it, a description of the shot, the shot's status, etc.
It seems to me best to group essential data about the shot into it's
own table, then create child tables which describe more specialized
information on the shot -- associated costs, it's timecode in the show,
etc.
So, does it also make sense to imagine each table and child table being
an class and subclass of the basic vfxShot type?
What is the standard procedure in designing a database application.
-- also, I've noticed the MySql-Cocoa development project. Anyone here
have any experience working with mySQL/Cocoa? Good match? Happy times?
Quick trip to hell? I've looked at Openbase, which was promising, but
need to keep costs down at the moment, as the implementation of the
software shouldn't grow beyond ten seats of simultaneous use -- but at
the same time I want to design a system that can grow substantially in
size...
Anyway, I'll leave it at that and see what people think. Thanks again
for the feedback -- absolutely invaluable.
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.