Hi. Did u look into the option of J2EE stores which has a new dbschema and proper indexing. It is not yet official part. But it is in the mail listing. Look for J2EE Store..
-----Original Message----- From: Wendt, Alexander [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 7:49 AM To: [EMAIL PROTECTED] Subject: nonoptimal database-schema Hi. I'm working with slide to deliver a framework to manage documents from 300 peoples (Filecontentstore to filesystem & remain to MySQL). The first time I saw the JDBC-store-defaults, I wonder why the tables didn't had any ID's (exempt from 'locks') and instead of ID's I saw many URI's. I couldn't believe anyone develop such a redundant db-schema. The webdav-server I tested before was catacomb, so I was a little bit disappointed. I accepted this blemish because of the big support of webdav-features. Now that I'm finishing developing some absentee tools to manage the user, groups, acl & a GUI to search for metadata, I got stocked in big performance-issues. After optimizing my code it was time to look at the db-structure. I really hope that, for the next version, anyone could spend an hour or two for a new DB-schema (and a few more for changing the java-db-interface), because, only with some added indexes I got many improvements in using my tools & with basic webdav-slide.
