Please consider that a project management app could have it's own table and relationships (if necessary) to other data I don't think that files should be stored in the db .. consider a table of meta data (creation date, modification date, creator, summary, etc) that also includes a link (a location url) to the file itself. A lot of this info can be extracted from the file itself so wouldn't even need this data stored in the table .. if the directory of such data was stored in the db, the ui of such an app could access this file data directly (especially for openoffice data files) Not sure how this would be affected by CVS concepts though (I guess we should leave something for the app developer to decide) Eric Wilhelm (ewilhelm@xxxxxxxxxxxxx) wrote: > > >> The following was supposedly scribed by >> Lee Fickenscher >> on Thursday 15 May 2003 08:43 am: > >>A project management module is an awesome idea, and definately a must >>have... Making it extensible to include files that relate to a project, >>but aren't specifically drawings, such as legal papers and what not, >>would be a real attention getter. > >Should this be included in the database or could a more suitable, existing >format be utilized? The ideas which I mentioned before about using a tarball >to store standard file formats together were driven by exactly this same >need. Would it be better to just store the legal papers as xml or some other >more text-oriented format? Maybe they are stored in this format in the >database (instead of in a tarball?) > >I think this may also be an application of the VFS (or temp file or whatever), >since you wouldn't really expect a word-processor to be built against the >database access library. > >--Eric > -- Brian Johnson This is where my witty signature line would be if I bothered to edit this line :)