4 ms·

Thanks for pointing that out. Safe to assume views go in the “code” schema with procs/funcs/packages, leaving just tables and sequences (if needed) in the “dat

• marcosdumay 6y ago
  I work with one codebase similar to that (DBMS only), and that's exactly what I do there (it's not that clear-cut, some code validates data, some data is short-lived). There is more than one "code" schema, with different lifecycles too. There are plenty of interesting problems with it. I would prefer to completely separate code from data if it wouldn't impact elsewhere. As it is, separating them would severely harm us, so it's kept this way. It brings a lot of productivity, but we have a very small team working on it, and completely separated procedures for them.