Hello and thanks.

In fact it worked that way, an all-uppercade handle.

Best regards.
Mario Guerra - NIC-CR

De: Jiří Morariu <jiri.morariu@nic.cz>
Enviado: martes, 16 de julio de 2024 05:39
Para: fred-users@lists.nic.cz <fred-users@lists.nic.cz>
Asunto: RE: A curious behaviour for a FRED client
 
Hello Mario.

Thank you for letting us know about an issue related to lowercase chars
in registrar's HANDLE. We can reproduce it. The reason of this behavior
is the fact FRED uses UPPERCASE handles (except of the fqdn) including
registrar's one. Clients (fred-admin and FERDA) ensure the HANDLE is
stored to the fred DB in UPPERCASE.

We strongly suggest to use UPPERCASE registrar HANDLE. Here is a DB
constraint that should prevent non-standard input. We must warn you,
however, that you should definitely NOT run this constraint during
traffic. Ideally, we recommend scheduling a downtime and running this
during that downtime. We also recommend that you create a backup of the
database before running it.

Let us know how it went, and do not hesitate to contact us in case of
any problems.

Normalize data that does not fit the new constraint:

```
UPDATE registrar
    SET handle = TRIM(UPPER(handle))
  WHERE handle != TRIM(UPPER(handle));
```

After data normalization it is possible to create new constraint:

```
ALTER TABLE registrar
        DROP CONSTRAINT registrar_handle_check,
         ADD CONSTRAINT registrar_handle_check CHECK(TRIM(UPPER(handle))
= handle AND handle <> '');
```

Best regards

--
Jiří Morariu

System administrator
---------------------------------
CZ.NIC, z.s.p.o.
Milešovská 5
130 00 Praha 3

e-mail:      jiri.morariu@nic.cz
web:         https://www.nic.cz/
---------------------------------

_______________________________________________
fred-users mailing list -- fred-users@lists.nic.cz
To unsubscribe send an email to fred-users-leave@lists.nic.cz