Good point. I wasn't thinking of a tool to validate arbitrary SQL
statements, but one that could validate a D model's correspondence with
the database schema. Presumably the queries would be generated by the
library.
what i like to see here are both parts - staticaly checked (if possible)
for faster development - but also runtime checked (maybe in form of an
check-mode)
for example:
you've got a varchar(12) field - how many times have you seen an check
for the inputsize not exceeding the 12 chars?
or datetime, etc. not all databases got the same range for special type
values
but something like that could be to database/version specific
