[cad-linux] Re: database access methods

Brian,
I agree with you. It should be handled somewhat like the Linux kernel
with device drivers. It's a good model imo.. 
There is stuff in the kernel that get's there "by invitation only".
Device drivers get contributed and the kernel makes mends to integrate
them and make them work well. So that's an idea for a PSM kernel and
applications based upon that. 

Roland

--- Brian Johnson <bjohnson@xxxxxxxxxxxx> wrote:
> 
> I thought part of the concept was to make the storage system easily
> expandable
> 
> I thought that the ability for an app to make it's own tables within
> the project db
> provided that.
> 
> I didn't think that the standard had to include a precise description
> every bit of
> data that anyone could ever possibly think of putting in the db
> 
> I also didn't think that for someone to add info that was not already
> specifically
> included in the standard complete with access library functions call
> to read/write
> to it would require the approval of the standard committee and and
> formal inclusion
> in the standard.
> 
> I do think that this approach will kill this initiative since it
> would require
> anyone who wished to use it for data storage for any objects other
> than for what it
> is already designed to get "permission" (aka inclusion in the
> "standard") to be
> allowed to do so.
> 
> I can understand such a strict standard for parametric object data
> but if there is a
> project db, there is other info that would be useful in there that
> perhaps doesn't
> need such tight controls
> 
> If there is a db per project, the ability to add additional tables
> for custom data
> is a really good feature.  Whether that additional data format is
> published or not
> (for other apps to use) should be irrelevant if it is stored in a
> separate table
> 
> IMO, the "standard" should apply to the base tables required to get a
> working cad ui
> and should allow (how would you prevent this anyway?) and anticipate
> the addition of
> other tables
> 
> I also still don't realize that native storage in a parametric format
> is "better"
> than storage of smaller building blocks and have a seperate table of
> the parametric
> objects that the "kernel" could use to mainpulate the smaller
> building blocks but
> perhaps that is simply because I can't fathom how it would work in my
> business where
> we do road design, sewer design, site design, building design,
> structural design,
> machine design, electrical design. How can a parametric model be
> designed to handle
> all objects including drafting devices like text, tables, borders,
> leaders, etc
> 
> 
> 
> 
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

Other related posts: