From: Paul G. <pa...@la...> - 2002-02-28 17:55:36
|
Quoting Bogdan Stancescu <mg...@fx...>: > Yes, that's it. And you could also back up the whole OPT directory just > in case - it only takes about 300KB compressed so it's worth it - data > types and field names in the database may change in future versions and > you'd be unable to make the new OPT work with the old database. Note this might change in a future version of OPT. At least one customer of ours has requested the option to store documents in a file system (e.g., SAMBA) which is under OPT's control, so they can also access the files from Windows. OPT could then compute a MD5 checksum for the file (and keep an archive copy in the database!) to check in any changes automatically, so there will be a change management process. Users opting to store files in a file system will need to have a location where permissions can be shared between OPT and SAMBA. Perhaps such files can have a checkbox and a path to the file location. Of course, we can't stop users deleting the file, or changing its name -- but that's why we take an automatic backup into the database after every MD5 signature changes. Anyway, bottom line is that the database will STILL contain all the necessary files, including maybe multiple versions! Another topic: database abstraction layers. I think ADODB is quite good but there are other possibilities, like PHPlib. What do others think will be a good choice to abstract the database, so we can add support for PostgreSQL or even Oracle? cheers Paul ********************************* Paul Gillingwater, BA, BSc, MBA Managing Director CSO Lanifex Unternehmensberatung & Softwareentwicklung G.m.b.H. NEW BUSINESS CONCEPTS E-mail: pa...@la... Tel: +43(1)2198222-20 Fax: +43(1)2198222-11 Mobile: +43(699)1922 3085 Webhome: http://www.lanifex.com/ Address: Praterstrasse 60/1/2 A-1020 Vienna, Austria ********************************* |