I added a new attribute to the Asset table as well as created a lookup type for it and added the lookup to the new attribute. Later I created a new class derived from Asset and added some data to test this. (this is a new implementation and no "real" data exists yet)
I later decided that the new attribute is not really needed and tried to delete it but could not because both associated table and the lookup had already been populated.
So, I ended up dropping the attribute column from the Asset table, as well as the new table that inherited the new attribute, not thinking of the fact that it has already been inherited and that it had lookup reference. So, I did my best to clean up the database as much as I could find any references to the deleted attribute.
However, the front end still showing me the deleted table, which I verified is no longer in the database and it also shows me the attribute that has been deleted.
The only clue that I have to go with is an error that I get when I log in to the management module, which is an SQL error. There is a query that joins the asset table with all of the lookups and all the columns it thinks need to be displayed in the asset list and this query gives me an error on the specific column telling me that it is not a valid column.
Is there a way to debug this and clean up the interface?