15 Mar 2005 05:33
Re: Re: 3D/4D with Base, or is there something else?
Jacob Floyd <techgurufloyd <at> gmail.com>
2005-03-15 04:33:33 GMT
2005-03-15 04:33:33 GMT
OK, I ended up staying up till 3 in the morning thinking about the problem. This e-mail kind of queued me into where I need to go and I think I finally understood relational databases, and how this relates to my problem. OLAP is for analysis of data, not inputing it, though I'd really love to be able to do something like "inverse-OLAP" putting in the data, in a way that makes sense, or in the same way we view it. Maybe if I'm ever lacking in a project to complete I'll work on doing something like that. Until then, i'll make do. So I have developed a design for a relational database that meets my needs. I found that with a relational database (after I figured out what I was doing) I could add some of the extra info into the database that would have seemed slightly out of place in my cube design, though it is very easy to see how a cube still applies to alot of the data. In the end, my design is a 12-14 table database (there are still a few questions on how I want to deal with a category of information). It's still got 4 dimensions, but I added several tables to further categorize and deliminate some info on all my info. Once I've finished putting it in digital form, I'll post a link to my desing, and a link to the final interface as I will want help populating it. My main table consists of a lists of IDs from 5 other tables essentially creating the "Array" that was mentioned. The purpose of this database? to create a central storage place easily accessible to more than just me for all of the toolkit API calls for a specific feature(widget) on a platform. So my 4 'dimensions', and subsequently the 4 main tables linked into my main reference(Continue reading)
RSS Feed