Oh yes,
Brandon read my mind. That was what I meant.
Think of the view "navigation" as an abstraction layer for your data, rather
than it containing the data. That is one of the pros for views: You can
abstract your complex, but robust data model beneath them and you don't have to
care about t
Hi Alex,
Without going into details about your data model in general, then in your case
I would probably create two different navigation tables: one for html and one
for scripts. Then I would be able to create reliable foreign key constraints.
Then, if I wanted a convenient way of selecting all
