i get that the underlying postgres table is not the same as what is exposed in labkey.

at least as it appears in the schema browser, the build-in table exposed by labkey is called auditlog, not audit. this would suggest that creating an external schema called 'audit' would not collide, but this does not seem to be true.

in the above post, I defined two external schemas, both of which pointed to the same underlying postgres table. for some reason, by giving one of them the name 'audit' it seems to inherit the behavior of the build-in auditlog table. I think this means that it probably should not be possible to define an external schema called 'audit'.