Hi,
What is the best practice for extending an existing table? Is it possible to add "user-defined" fields to existing tables, (and if so, what are the naming conventions & procedures, etc), or do we need a custom "local table" that has the same key to provide a one-to-one linking between the standard Tessitura table and our local table? If this is the case, then is there any automation provided by the Web API that will return our custom fields, or must I also build local procedures, call those separately, and join the tables logically in code after retrieving the data from the standard Tessitura web API, and our local procedure API call?
One example would be to provide 3 custom fields for the "TR_Facility" table. Tessitura wouldn't use this data anywhere, but we will use it on our web site.
Thank you,
Larry
Thanks, I'll look into the suggestions and report back with what our solution turns out to be.
Larry,
This is a little bit of a next level solution, but in a previous life I worked with a CRM package that allowed the DBA to effectively do what you mentioned in your initial question. They created a separate table to match each standard table (i.e. t_customer_ext) which they tied together with triggers so that any row in the parent table created a record in the extended table. The local DBA was then free to add any fields they wanted to the extended table (effectively modifying the base install) without worrying about a future upgrade wiping out their changes.