|
From: Ben A. <be...@th...> - 2002-05-24 10:52:17
|
I'm building a information and workflow system onto an existing relational schema, which is fairly complex (around 25 tables), and which has three types of user with different roles, but whose activities use and affect the same tables. I'm wondering the best approach to structuring the packages and objects? I thought of making a package for each user's activities (there is very little shared functionality), and making each table into a SPOPS object (with any more complex activities handled explicitly with SQL) but then which packages should the common tables belong to? Could I make a separate 'schema' package which contains all the tables as SPOPS objects? any ideas gratefully received ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ben Avery YouthNet Programmer/Analyst Broadmead House e: be...@th... 21-23 Panton St t: 020 7925 2530 London f: 020 7925 2830 SW1Y 4DR ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |