Database Architecture
Posted by jobber on June 20, 2008
Today we built up a class system to describe the basic objects we intend to use in the core of the ROA project.
Our conversation in Dunkin’ Donuts yesterday pertained to what structure our database should take to efficiently and effectively back the core of the project; today’s work flowed out of this discussion, as we created a class for each table we envisioned yesterday.
I learned a lot today about the @OneToMany relationship today, inescapable in a project that uses lists.
We also plan on using a lot of middle-man tables that include items that each include a pair of ids — that of two other “real” objects. This allows two different objects that each can point to many instances of the other object type — for instance, a prayer list can be referenced by many groups, but each group can reference many prayer lists. Each of these items has a one-to-many relationship to the ‘list-permissions’ table. Each item in the latter table has two many-to-one references back to group and list items.
Cool gadget combination of the day: remote desktop and voice recognition. I still jump a little each time Mr. Chandler says “wake up!” at his desk across the room. It’s only when he goes on to say things like “mouse grid…” and “press F8″ that I realize he is using his voice recognition software, and was not, after all, under the impression I was snoozing. If it’s cool to be able to talk to your computer, just think how cool it is to talk to someone else’s computer! Mr. Chandler and I make use of VNC almost everyday, allowing him to see and control my box without having to walk across the room and trade chairs with me. today we tried out the voice recognition in conjunction with VNC, with success.
