3 ms·
Another alternative is one of the PICKs where the source code is (used to be perhaps) stored in the database, or I think COBOL on some systems didn't exactly le
by floaterpig 9y ago
Another alternative is one of the PICKs where the source code is (used to be perhaps) stored in the database, or I think COBOL on some systems didn't exactly lend itself to flat files from the little I saw (or at least the OS wasn't embracing CVS/SVN/Git in favour of some hugely expensive and utterly inferior product...).
- Terr_ 9y agoAh, right, or "business logic eval()ed from database text" systems.
- jupp0r 9y agoOr, more commonly - stored procedures.
- Terr_ 9y agoStored procedures are a little easier to handle provided your deployment system does a wipe/replace, similarly to overwriting scripts/executables. I was thinking of a grimmer scenario, where the system has an disquieting aspect of polymorphic, run-time code editing... central to its "flexible" production behavior. There are more things in heaven and earth than dreamt of in sane philosophy.