Massimo Dal Zotto <dz@cs.unitn.it> writes:
> It is nice to provide smart date interpretation in the backend but in
> order to be really Y2K compliant we *MUST* forbid any ambiguous date
> format in the backend.
Why? Has some bureaucrat somewhere defined "Y2K-compliant" as meaning
"thou shalt stop accepting 2-digit years"? I have not heard of any
such definition and I am entirely prepared to ignore it if it exists...
it has nothing to do with reality.
regards, tom lane