
Ten Signs Your Excel File Needs to Become a Database
Ten concrete signs that an Excel file has become a database, from several editors to lost updates and broken lookups, with a quick test for each.
Tag
590 posts

Ten concrete signs that an Excel file has become a database, from several editors to lost updates and broken lookups, with a quick test for each.

Test a generated Excel report with pytest: structure, control totals, formulas, formats and edge cases, plus a fixture of bad input and a golden file.

Define a block once with an anchor, reuse it with an alias, and merge it with the merge key. Real output shows overrides, sharing and where merging stops.

Block and flow styles for sequences and mappings, lists of mappings, empty collections and why a missing value is None, each with its parsed result.

The pipe keeps line breaks, the greater than sign folds them, and chomping indicators control the final newline. Six variants and the exact strings.

Plain, single quoted and double quoted YAML strings compared, with the characters that force quotes and a table of values that silently change type.

Pull records out of a SOAP response with lxml: mixed-namespace children, xsi:nil, empty versus absent, repeated nodes and exact decimals.

Compile a stylesheet once with lxml, pass parameters safely, read xsl:message from the error log, block file and network reads, and know the 1.0 limit.

Pass values into XSLT from xsltproc and lxml, and see why a param that looks like a string is read as an XPath expression and silently ignored.

Sort with xsl:sort and filter with XPath predicates in XSLT, and avoid the default text sort that put 250000 after 44.00 and 29.50. Multiple keys and case.

Group 20,000 invoices by currency with a Muenchian key in XSLT 1.0 and with for-each-group in XSLT 2.0 on Saxon, with sums, counts and timings.

Build and read JSON in Bash without breaking: jq --arg instead of string concatenation, newlines in values, exit codes, null as text and filter injection.