[Info-ingres] Bad dates

[Martin Bowes]

Hi All,

This has just been pointed out to me...

The user created a table with an incorrect date default, a result of bad typing...

create table wrong(a integer4 not null not default, b ingresdate not null with default 0)\g
...and that worked.

They only found out about it when they went to use the table.

insert into wrong(a) values (1)\g
E_US10CE '0' is not a valid date/time value.

So, typically if we create a bad default the system objects at the create, which is desirable.

While I understand that checking the default date is valid in all input date formats would be nigh on impossible and better to allow the user to get a usage error and get them to fix it, nonetheless zero can never be a legitimate ingresdate in any format I can think of.

So is this a bug or just a case where the user has to get their own way out of this?

Martin Bowes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20210426/21443ad9/attachment.html>