On 7/11/07 8:55 PM, "Joe Wilson" <[EMAIL PROTECTED]> wrote:
> The problem is schema design.
> Just use a single task table with another key column for the task number.
> Queries on N task tables with UNIONS are killing your performance.
>
But how do I associate processes to different tasks
The problem is schema design.
Just use a single task table with another key column for the task number.
Queries on N task tables with UNIONS are killing your performance.
--- Bharath Booshan L <[EMAIL PROTECTED]> wrote:
> TaskN_table
> | Name | TaskID |
>
> TaskN_info_table
>
> | TaskID
Hi All,
Following are the table structures I am using in one of my application
System_table
| Name | SystemID PRIMARY KEY |
Process_table
| Name | SytemID REFERENCES System_table | ProcessID PRIMARY KEY |
ParentProcessID | IsParentProcess |
Each process represented by UNIQUE ProcessID
3 matches
Mail list logo