• Sign In
  1. Messages

suggestions on most efficient way to move labkey lists into hard tables?

LabKey Support Forum (Inactive)

View Message

view list print
suggestions on most efficient way to move labkey lists into hard tables? Ben Bimber  2010-12-13 06:59
Status: Closed
 
in the EHR we have a number of small lists that serve as lookups for various other tables. moving these into hard tables has seemed to provide a not insignificant performance improvement. two questions:

1. After migrating lists into hard tables, what is the most efficient way to update metadata to reflect these changes. Anything that is coded in files can be modified in intellij (primarily the query metadata xml files). Things like list and dataset definitions are not. Is there a good solution to update the latter? Are there other places I am not considering that might need to be updated to reflect the new lookup targets?

2. Is there an efficient way to study-wide identify any broken lookups? Query validation handles many potential problems, but I do not think it would catch a bad lookup if that field doesnt appear in the SQL (unless i'm mistaken about something).

Thanks for the help.
 
 
jeckels responded:  2010-12-14 16:18
Hi Ben,

1. Do you mean update lookups that used to point to lists.<list_name> to <external_schema>.<list_name>? We don't have a UI for bulk updating across lists and datasets. You could query directly against the Postgres database to at least track down the ones that need to be changed:

SELECT * FROM exp.propertydescriptor WHERE lookupschema = 'lists'

2. Query validation won't detect broken lookups, unless they're used as the special <table>.<column>.<lookup1>.<lookup2> syntax in custom queries. I can't think of any reasonably easy automated way to track them down.

Thanks,
Josh